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

Tomato 1.14 bug?

Discussion in 'Tomato Firmware' started by siimo, Jan 25, 2008.

  1. siimo

    siimo LI Guru Member


    This is the first time ever since I got my WRT and put Tomato on it has something gone wrong and had to reboot it to get it going.

    Basically it couldn't detect my DSL modem which is configured to use DHCP on the WAN port out of the blue. It had been connected and working for two days and had been working ok. Usually when this happens the DSL modem is the culprit so I rebooted that twice but still no-go, WRT could not get a DHCP lease from it at all for some reason. So I had to reboot WRT and it finally started working. :thumbdown:
  2. AeN0

    AeN0 Network Guru Member

    1.14 have some bug with udhcp. Try 1.13.
  3. roadkill

    roadkill Super Moderator Staff Member Member

    try Advanced-> DHCP / DNS -> Reduce Packet Size
  4. mstombs

    mstombs Network Guru Member

    I did try that - 1.14 is unusable with my half-bridge modem which uses 60second lease. It does not renew at half lease time - it did renew eventually after lease time has expired, the IP address is dropped and all connections broken! Logging is also broken in 1.14, probably related coz new check box to disable dhcp messages has been added and too new busybox is used.
  5. digitalgeek

    digitalgeek Network Guru Member

    try clear nvram and reconfigure the WRT... (don't restore the config from a backup)
  6. siimo

    siimo LI Guru Member

    thanks for the tips. I am trying the reduce packet size first and has been fine for a day now. Want to avoid clearing NVRAM if possible as i have a few QoS, access restriction, port forward rules etc.

Share This Page