1.19 -> 1.20.8002, now NSLU2 won't accept DHCP lease...

Discussion in 'Tomato Firmware' started by bripab007, Jul 25, 2008.

  1. bripab007

    bripab007 Network Guru Member

    To start off, the Linksys NSLU2 has always been a little finicky with DHCP because the stock firmware is coded to always try to get, meaning it's sometimes would just become unresponsive if it didn't get that IP.

    When running DD-WRT and now, Tomato, my WRT54G would always try to give it, and so I was usually able to boot the NSLU2 up, let the router see it in DHCP, attempt to give it the .131 address, then go in and set up static DHCP with the .77 address and reboot the NSLU2 and everything was hunky-dory.

    I just upgraded to Vic-Tek's 1.20.8002 build last night, and the first thing I noticed after re-configging my port forwards and such was that I couldn't get to the NSLU2's FTP from outside the network. Thought at first it was a port forward issue, but then noticed in the device list that, even though I'd created the address entry in Tomato's static DHCP for the NSLU2, in the device list, it was not showing up with a least time remaining, like all the other hosts on the network. In Tomato's log, it shows that it just keeps doing DHCP Offer and DHCP Discover commands to try to give the NSLU2 that address I guess, but it's not taking it, like other hosts would.

    So I tried removing the static DHCP entry for it, rebooting the device, and again, DHCP Offer/Discover, but this time with the address, but it won't take that either, it's somehow keeping a static setting (which is similar to what it's always done, but I was usually able to make it snap out of it with the static DHCP entry).

    Is there a way I can tell DNSMASQ to just offer it by default instead of, without using the static DHCP entry, or is that entirely up to some random algorithm DNSMASQ uses or something?

    For what it's worth, if I config the NSLU2 to have a static IP of .77 and have the router entered as its gateway, the external port forwarding does work, so I have a work-around, but I'd like to be able to get static DHCP working again, like it was before, and as all my other hosts are.

    Thanks for any suggestions/help :)
  2. Victek

    Victek Network Guru Member

    Strange... I have and NLSU2 too.. no problem.. please do a nvram erase.. remember the procedure I wrote in my post. :biggrin:
  3. bripab007

    bripab007 Network Guru Member

    Yes, I initially forgot to the do the NVRAM erase after initial upgrade (did one before the upgrade), then noticed some quirks and remembered you said to erase after.

    Do you know of any updates/changes to DNSMASQ or the way it behaves, aside from the DNS security fix? Something that might affect the way clients get DHCP leases?

    Suppose I could always do another NVRAM erase and then a 30/30/30 and try it again.
  4. Victek

    Victek Network Guru Member

    Nvram erase through the option in Restore default configuration is enough cause a reboot is performed in parallel. Under my opinion .. DNSmasq 2.45 is working very well, I don't think this is the origin of this behaviour. I forgot to advice you a new configuration from scratch, not using any restore configuration file.
  5. bripab007

    bripab007 Network Guru Member

    Yes, I reconfigured manually after upgrading to the new firmware; I did not restore from a config. file.
  6. mstombs

    mstombs Network Guru Member

    I've seen something in the nslu2 documentation that static IP was preferred, but I ignore that and have it set to auto, and never had an issue with up to Tomato 1.19 (waiting for all the beta testing to finish before upgrading... but I will, can't have my modem using a newer version of BusyBox than my router for long...)
  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