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

Is this a firmware bug?

Discussion in 'Tomato Firmware' started by vanhh, May 11, 2008.

  1. vanhh

    vanhh Network Guru Member

    Hi guys,

    This is my set up - linksys router WRT54G, motorola modem 2210-02-1002. Modem does PPPoE and router DHCP. Modem IP address is Router IP address 192.168.2.xxx, subnet mask I set them up this way to get to the modem stats. The weird thing is I could not get to modem after I shut my computer off over night. So every day I have to go into my router to release and renew my router IP address on the WAN side. I'm able to get to my modem fine after that. This is only happened when I turned my computer off over night. My router and modem are on all the time. So is this a bug in tomato 1.19 firmware?

  2. LLigetfa

    LLigetfa LI Guru Member

    You can get modem stats if the router does the PPPoE. That's how I have mine.
  3. vanhh

    vanhh Network Guru Member

    I don't have problem getting the modem stats. Please read the question. And even you have router does PPPoE, you wouldn't be able to get to this motorola modem, if you don't have the right setup. My question is why do I have to release/renew router IP address after I shut my computer off over night eventhought my router and modem on 24/7? Is that the firmware's bug?
  4. LLigetfa

    LLigetfa LI Guru Member

    You made a statement. I countered it. That's all.

    Look at your routes on the PC both when it works and when it doesn't. I doubt it's the firmware's fault your PC doesn't know the route.
  5. vanhh

    vanhh Network Guru Member

    Please give someone else a shot at it.

  6. mstombs

    mstombs Network Guru Member

    This can happen with half-bridge modems (the ISP WAN IP/ Gateway passed to the router), the modem forgets the route how to reply when accessed on its local IP address. I had an old cable modem that would only communicate with the router when it had a local IP address. A permanent fix was to add a secondary IP address to the router WAN port with something like

    ifconfig vlan1:0 netmask
    local IP address of modem was

    I later received a new cable modem which did not need this fix, but is accessed on same address.
  7. HennieM

    HennieM Network Guru Member

    To be clear vanhh, is this what you have?


    and the problem is that the modem(LAN)--(WAN)router loses connection, i.e. the router apparently does not request a new DHCP address from the modem?

    If so: A device that requested an address from a DHCP server will keep that address for at least the lease duration period. If the lease expires, and the device cannot re-contact the DHCP server, the device would still keep that address, because there's no other address to use.

    The problem you have therefore seems not to be that your router loses its address, but that your modem "forgets" the route to net 192.168.2.x (LAN side of the router), or something similar. The explanation offered by mstombs therefore seems quite feasible.

    A way to counter this may be to override, in the router, the period that the router waits to renew or re-affirm its DHCP lease. I don't know how to do that (but I'm sure somebody will... ;)

    A better way, assuming it's possible, may be to
    1) hard code your router's WAN address (say, and
    2) turn off the DHCP server in your modem, and
    3) hard code the static route "route netmask gateway" into your modem.
  8. vanhh

    vanhh Network Guru Member

    I don't think problem is lease time, because the lease time length is 1 day. I dont know if turn off the modem DHCP is possible or not. But I will be able to change the setting of the router from 'automatically DHCP' to 'Static IP' on the WAN side. I will give it a try to see what happens.

Share This Page