DHCP issues on wireless

Discussion in 'Tomato Firmware' started by nricciardi, Dec 17, 2007.

  1. nricciardi

    nricciardi LI Guru Member

    Folks, need some help here

    I installed Tomato 1.131252 (latest available) on a wrt54g v2.2 from the official firmware.

    Wired computers are working fine.

    But wireless is not getting an IP from DHCP when WEP or WAP is activated.

    Any hints?

    If I turn off WEP/WAP, DHCP works fine. Static IP on the notebook also works fine.

    WEP works fine with the official Linksys firmware.

    Thanks for any info.
  2. j.m.

    j.m. Network Guru Member

    Double and triple check that your client's WEP/WPA key matches that of the router. In my experience, that is usually the cause of the problem you described. If it still doesn't work, try each of the three NAT Loopback choices on the Advanced|Firewall page. Report back which, if any, help.
  3. nricciardi

    nricciardi LI Guru Member


    I'll check.

    But if the WEP key does not match, how do you explain the fact that wireless work if I put a static IP on my notebook?
  4. j.m.

    j.m. Network Guru Member

    Overlooked that. Sorry. By work, you mean it actually pulls up web pages etc., right? Then you must have the correct key. Try playing with the NAT Loopback setting. There have been some reports that "Disabled" can interfere with DHCP. Try each of the 3 options and see if one works.
  5. paped

    paped LI Guru Member

    Not sure what NAT loopback would be used for if you are only picking up an IP address from the router DHCP server, NL would normally only be used to loopback web connections i.e you go to a your web URL that terminates back on your router????

    Anyway re the problem is your PC XP?? If yes have you manually setup the wireless connection or used the wizard? If you did it manually go in to the wireless windows delete the manually setup connection and use the wizard as it seems to fix most XP wireless problems, basically XP and manual wireless setup seems a bit flaky to say the least.....
    If this still does not work delete the connection again try going in to "services" in windows and disable the wireless zero config service then try the wizard set again...

    Hopefully this will get you going.....
  6. j.m.

    j.m. Network Guru Member

    I'm with you. However, in the course of discussing the new NAT Loopback option in the 1.13 thread, someone pointed out that the Tomato FAQ says that some users in the past reported problems getting their wireless clients to grab a DHCP IP when NAT Loopback is disabled. Go check it out. Like you, I find that a bit puzzling. The only thing I can think of is that, in the Linksys code and possibly in older versions of Tomato, "disabled" inserted an iptables drop rule that could have affected DHCP for wireless clients since wireless traffic ends up going the the router.
  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