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

WAN DHCP won't renew?

Discussion in 'Tomato Firmware' started by dmb41crash, Jul 11, 2010.

  1. dmb41crash

    dmb41crash Networkin' Nut Member

    Firmware: TeddyBear v1.27.8747 ND Std
    Router: WRT54GL v1.1
    WAN Connection Type: Cable DHCP
    WAN Lease Time: 7 days

    In a nutshell, when the 7 day lease expires, the router disconnects. I have to manually renew it. The log shows a bunch of "Sending renew..." messages over the course of the 7 day lease (I believe starting at around the halfway point of expiration) with no other action taken.

    This can't be right, and I can't be the only one experiencing this problem. I had an old piece of crap BEFSR41 on the same cable line with the same modem for 8 years that never failed to renew and never dropped the connection, sometimes going months without a reboot or user intervention. This has to be a Tomato bug, yeah? Everything else on the router works as it should.

    I've tried all the standard troubleshooting to get it to work, including multiple hard resets and NVRAM clears, the problem persists both with the default Tomato settings as well as my own setup. :frown:
  2. kobik

    kobik Networkin' Nut Member

    I had similar problem till I've upgraded Tomato to 1.28.
  3. mstombs

    mstombs Network Guru Member

  4. dmb41crash

    dmb41crash Networkin' Nut Member

    If there weren't a few features in TeddyBear's mod that I've come to rely on, I would definitely give the official firmware a try. To make things worse, TeddyBear stated the other day that he has put development of his mod on hold for the foreseeable future, so there's no telling when his releases based on 1.28 will come out.

    Ah, interesting, thanks for the link! I searched "DHCP" on this board and found a few articles referencing similar issues, but it seemed as if those were problems with PPPoE...perhaps not. I will definitely take another look at the iptables solution and see if that works. In the meanwhile, I planned on working around the problem by having a "reconnect" scheduled task set to run once a week just before the lease was set to expire.

Share This Page