Alchemy port triggering broken?

Discussion in 'Sveasoft Firmware' started by _Shorty, May 10, 2005.

  1. _Shorty

    _Shorty Network Guru Member

    port triggering doesn't seem to be working in Alchemy 1.0, anyone given it a try? I usually use this to forward gnutella traffic on port 6346, but it doesn't appear to work. Keep appearing as though I'm a firewalled client, which I should not when using port forwarding. If I use the regular 'port forwarding' to do this for my current IP then it works as it should, but using port triggering doesn't appear to work at all.
  2. littlewhoo

    littlewhoo Network Guru Member

    Well, usually I'm not using port triggering and I don't know about gnutella. But I just did a quick test with IRC/IDENT and port triggering seems to be working for me.
    The only entry on the port triggering page for this test was
    Triggered Range: 6660 - 6680
    Forwarded Range: 113 - 113
  3. _Shorty

    _Shorty Network Guru Member

    well, it was working fine with HyperWRT, and I just used the exact same settings I did there in Alchemy and it doesn't work for me on my GS 1.0 so I don't know what to say.
  4. Olinka

    Olinka Network Guru Member

    Works for me too.
    Alchemy 1.0
    triggering port 21,
    forwarded range 20
    WRT54G 2.0
  5. _Shorty

    _Shorty Network Guru Member

    well, it most certainly isn't working for gnutella/ed2k traffic and Shareaza here. I always get a LowID for ed2k if I try to use port triggering, which means it isn't working. With HyperWRT it works just fine and I get a HighID on ed2k every time, which means it is indeed triggering and forwarding the port. If you have a few spare moments, snag Shareaza from and put 6346-6346 as the trigger ports and forward 6346. Definitely not working here with Alchemy.
  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.
    Dismiss Notice