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

WRT54G port forwarding.

Discussion in 'Cisco/Linksys Wireless Routers' started by Anonymous, Apr 5, 2005.

  1. Anonymous

    Anonymous Guest

    Hi all, I've been searching the internet for a few days now, trying to sort out how to enable port forwarding on my new WRT54G router (running wired).

    I looked at portforwarding.com, but the instructions must be for an older version of the router.

    Anyway, i did what seemed obvious, set the start and end port correctly, the IP address to the local IP of my computer (192.168.1.100), and enabled it, but i keep getting a NAT error from Azureus.

    I've read that NAT errors are indicative of incorrect port forwarding, yet the forwarding page in my router setup seems to be configured correctly.

    I'm thinking it could be Azureus, but i'm not sure. Is there a reliable way to test whether port forwarding is working?

    Thanks in advance,

    Hugh
     
  2. Anonymous

    Anonymous Guest

    Oh, I also have DHCP enabled. Which, as I understand, assigns an IP address automatically to each computer on my network?

    Now, i've read in a lot of articles that the IP address must be made static before port-forwarding will work properly.

    As it is, my computers IP remains static at 192.168.1.100, but is it necissary to *make* it static through the connection properties, and assign an IP address manually?

    Hugh
     
  3. Anonymous

    Anonymous Guest

    I would like to add to this question, inquiring about basic port forwarding for a web server which automatically recieves a static address from the WRT54G.... An extended tutorial will aid those seeking immensive information for basic port forwarding......
     
  4. Anonymous

    Anonymous Guest

    config

    i need an answer to this as well..some one email me
    scizzorslikewhoa@gmail.com
     
  5. cromrell

    cromrell Network Guru Member

    dhcp vs static ip

    I would suggest that if you are going to port forward, that you assign your device a static ip address -one outside of the DHCP range.

    DHCP works great, it dynamiclly assigns and manages ip addresses and eliminates all of the tracking, and duplication which can occur if you manually assign ip addresses.

    However, if your PC happens to have 192.168.1.100...
    and your web server happens to ahve 192.168.1.101

    Turn both of them off (power failure, etc), and then turn your web server on first. The router will DHCP and give the web server 192.168.1.100. Then your port forwarding would be pointing to the wrong device (ip address).

    I haven't tested yet... but the router firmware might be preventing you from port fowarding to an address within the DHCP range.

    Chris
     
  6. Anonymous

    Anonymous Guest

    no, it won't. if the lease is still valid when the system reboots, the client will send a request to use the same IP address and network configuration information. the DHCP server will permit the request if the address is still available, and it will be if the number of clients on your network is less or equal than the assigned IP range. on an NT machine you'll have to do an 'ipconfig /release; ipconfig /renew' on the corresponding interface to apply for a new address.
     
  7. Guyfromhe

    Guyfromhe Network Guru Member

    if the router reboots the leases disapear
     

Share This Page