1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

port forward/redirection not working

Discussion in 'HyperWRT Firmware' started by serioustommy, Mar 14, 2006.

  1. serioustommy

    serioustommy Network Guru Member

    Hi all,

    I've just recently purchased a WRT54GS V4, and loaded it with v4.70.8, Hyperwrt 2.1b1 + Thibor14

    Everything seems to be fine, except that I can't seem to get either port forwarding/port redirection to work.

    I've searched the forum but no one seems to have this problem, so I'm not sure if there's something wrong with what I'm doing or else.

    Here's what my setting look like:
    [​IMG]

    What I'm trying to do here is simply forward the emule and bittorrent packets to a PC on the network, which has a static IP of 192.168.1.100

    But it just doesn't work however, I'm using https://grc.com/x/portprobe=4662 to test for the port. Emule client also tells me that the port is not opened. Same with the bittorrent client.


    However, bittorrent port forwarding works with UPnP enabled! which look like this:
    [​IMG]

    What puzzles me is that it looks exactly like what I was doing manually! But since Emule doesn't have UPnP built in, I couldn't make use of this feature.


    Any helps that you could provide me on this is very much appreciated... I've been on this all day :(
     
  2. dvaskelis

    dvaskelis Network Guru Member

    I think I had similar problems, try it with the "Application" name 8 characters or less and no spaces.
     
  3. NateHoy

    NateHoy Network Guru Member

    Why do you have UDP 4662 and TCP 4672 forwarded? Which one of them is eMule using? I think the port numbers should be the same, with both UDP and TCP forwarded, right (or one forwarding set to BOTH)? Or is eMule different and uses different ports for TCP and UDP communications?

    Also, did you do a factory reset / erase NVRAM after the update? You may have some bad NVRAM settings hanging out there causing trouble.
     
  4. serioustommy

    serioustommy Network Guru Member

    I changed the names to "emule1", "emule2" and "bt" but unfortunately they still don't work :(

    Yes the default ports for Emule have different port numbers for TCP and UDP for some reason. I guess you can just manually set them to be the same but I just left them all at default for now.

    Yeah I did the "Clear NVRAM, restore factory defaults" after the update.


    The thing is, port scan shows that the packets to these ports are being dropped, and the port is not simply closed, so does that imply that maybe it has something to do with the firewall dropping the packets?
    Could UPnP port forwarding works because internally it opens up the ports at the firewall automatically?
    But I've checked the firewall setting and it doesn't have any options for me to open specific ports...
     
  5. Thibor

    Thibor Super Moderator Staff Member Member

    with regard to UPnP, that's exactly how it works. with respect to your forwarding issue, as long as your pc is 1.100 it should be working. how do you connect to the internet? is it direct or through a modem, is your modem blocking the ports? you can check the firewall status on the command line with "iptables -t filter -L", the forwarding entries are under "FORWARD". there is no reason that they shouldn't be there though, according to your screenshot. how is the static ip of your computer done? on your pc itself or via static dhcp?
     
  6. serioustommy

    serioustommy Network Guru Member

    I manually set my static IP on my windows machine, which is 192.168.1.100. However the DHCP is running as well on the WRT54GS router, so other PCs on the network can connect to the internet without fiddling with the network settings.

    I connect to the Internet by using a Draytek ADSL router. What I do is setup a DMZ which basically forwards everything from the Draytek ADSL router to the Linksys WRT54GS router.
    So I basically turned off all the features(including DHCP) on the Draytek ADSL router to make it not do anything besides routing all the packets to the WRT54GS router, and have all the PC clients connect to the Linksys WRT54GS router.

    Could this be the cause?
     
  7. serioustommy

    serioustommy Network Guru Member

    I followed your instruction and run "iptables -t filter -L", but I cannot see any entries I've entered in the port forward page, only the ones defined by UPnP is in there... What might be causing that?
     
  8. Thibor

    Thibor Super Moderator Staff Member Member

    you're doing a double nat setup, is the wrt connected to the draytek via the WAN port? the firewall loads it's rules after the wan interface is configured
     
  9. serioustommy

    serioustommy Network Guru Member

    Yes the Daytek router's LAN port connects to the WRT54GS's WAN port.

    At the Draytek router's level, the Draytek's router has an IP of 192.168.2.1 whereas the WRT54GS has a static IP of 192.168.2.10 assigned. The DMZ is set up on the Draytek router so that all traffic bypasses the firewall and goes straight to 192.168.2.10, which is the WRT54GS.

    At the WRT54GS's level, the WRT54GS has an IP of 192.168.1.1 and every PC connects to it has 192.168.1.*

    It seems to work fine, everyone can use the internet correctly. It's just the packet forwarding that doesn't seem to work. However, UPnP's packet forwarding seem to get by just fine so I don't understand the difference between the manually setup one and the UPnP setup one... :(
     
  10. Thibor

    Thibor Super Moderator Staff Member Member

    bottom line is, from what you've described...even with the double nat, it should be working; don't have a clue why it isn't
     
  11. serioustommy

    serioustommy Network Guru Member

    I decided to reboot the WRT but after restarting the internet connection went down for some reason. I could still connect to the WRT's admin page though, and all the settings look to be in order, and the status page shows that the WAN connection is up and running.

    Without much choice I did the "Clear NVRAM, restore factory defaults" option again and wiped everything clean. And guess what, after putting all the settings back in and going back onto the internet, the port forwarding that I manually specified starts to work! :D

    Anyway thanks people for trying to help me out on this, especially Thibor for developing this firmware!
     

Share This Page