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

VER. 1.13 poor uptime

Discussion in 'Tomato Firmware' started by starbiker99, Jan 11, 2008.

  1. starbiker99

    starbiker99 Network Guru Member

    I upgraded to 1.13 shortly after it was released and have noticed that I can't get my router to stay up longer than a few days sometimes a little as a day. I have a WRT-54GS V2. Has anyone else experienced this?
  2. Kiwi8

    Kiwi8 LI Guru Member

    Try to do a thorough NVRAM initialisation and reboot, see if the problem persists.
  3. dvaskelis

    dvaskelis Network Guru Member

    I have two Linksys WRT54GS v2 routers running Tomato 1.13 (one as WET bridge), both now up for over 21 days.
  4. der_Kief

    der_Kief Super Moderator Staff Member Member

    No problems at all with uptime here > 30days ! As Kiwi8 mentioned try NVRAM reset.

  5. apelete

    apelete LI Guru Member

    I noticed the same problem with a Buffalo WHR-HP-G54.
    Flashed with Tomato 1.13, it rebooted twice in less than 5 days. Same problem after NVRAM reset.
    Put my Buffalo back to 1.11 and it's been up for 13 days already...
    Don't know where the problem came from though, I was using 1.13 just the same way as 1.11, in gateway mode, with the exact same settings....:thumbdown:
  6. starbiker99

    starbiker99 Network Guru Member

    Last night I loaded DD-WRT RC 6.2 on my Buffalo and thought I would give my Lynksys some time off. I really got used to bandwidth feature in Tomato and will probably switch back later today. I may try to load the open VPN version and do a NVRAM reset before I do. If Tomato only had multiple SSID's it would be near perfect.
  7. tstrike2000

    tstrike2000 Network Guru Member

    1.13 for me has been up for 35 days. Besides clearing NVRAM initially, the only other time I've had problems with uptime is when I had the router save my Bandwidth Monitoring information to a CIFS client 3 or 4 times a day. Once I switched it to only save it once a day, the uptime has been stable.
  8. venk25

    venk25 Network Guru Member

    WRT54G V3

    Tomato Firmware v1.13.1252

    Time Fri, 11 Jan 2008 15:28:14 -0500
    Uptime 24 days, 00:34:34

    I've had poor uptimes when wireless is enabled - not just with Tomato, but with other flavor of firmwares too. I now have disabled wireless and the router goes down only if I reboot or there is a power failure.
  9. szfong

    szfong Network Guru Member

    It's a wireless driver issue, certain wireless clients will cause Tomato to spontaneously reboot or lock up. Upgrade your wireless client's drivers. Tomato 1.13 still uses a relatively older version of the Broadcom wl driver. A script which restarts the wl driver every once in awhile may also help. I believe latest openwrt/dd-wrt rc-6.2 do not have this issue because of their updated drivers.

  10. Mastec

    Mastec Network Guru Member

    On the 31st day of uptime with a WHR-HP-G54 loaded with Tomato Firmware v1.13.1252, three wired and three wireless clients.
  11. pharma

    pharma Network Guru Member

    No problems at all with 1.13 .....

    Uptime 25 days, 06:22:05


    I doubt Venk25's problem is due to Tomato's Wireless driver. His router is an older version WRT54G V3, as I have one even older without these problems. Too many rumours floating ....:rolleyes:

    @Venk25 -- Reinstalling a new driver might work, but see if changing some of your wireless driver XP options makes any difference. In the past I had connection problems and upon disabling the "Bluetooth" option my problem disappeared. Another option I changed was to enable a "G" wireless network only, instead of the default "B"/"G" network.

    Broadcom Wireless Adapter Guide - describes the different settings and what is default or optimal.

    The true test will be installing the previous version of Tomato. If you have the same problems then your issues might not be with Tomato, but you computer setup.

  12. starbiker99

    starbiker99 Network Guru Member

    I rolled back to Tomato 1.11 yesterday I want to see what kind of uptime I can get on it.
  13. venk25

    venk25 Network Guru Member

    szfong, pharma,

    I think its wireless driver issue, but not on clients - but the version on the router. See my post here. However, I could be wrong here.

    All my clients' wireless drivers are up-to-date and I have different types of wireless cards on WinXP/Linux systems (some dual-boot).

    szfong - I've tried the wireless restart script and it didn't help much. I thought of going back to OpenWRT (Kamikaze) or DD-WRT but the features in Tomato is preventing even the slightest idea of doing that - I love the features in Tomato.

    pharma, I'll try your suggestions sometime.

    I've seen the issue with various versions of different firmwares, including Tomato.
  14. szfong

    szfong Network Guru Member

    Yeah, it's a unique prob. Newer revisions of Broadcom chips has this prob. fixed. You may wish to get another router. Also, this prob. crops up more in high traffic areas where many different clients using many chipsets using different ver. of their client drivers. If its a small home environment, just get a new Buffalo, or WRT54GL, and you would be fine.

    Also, you may put it in client-bridge mode, connecting the problematic router to another AP, that way you should not see this particular issue of low uptimes. Sometimes downgrading to Thibor15c, may also stop the low uptime issue. Anyhow, I put Tomato mostly on WHR-HP-G54 units, and old problematic units use dd-wrt v24 rc-(5->6.2) & openwrt. You may wish to this while patiently waiting for if/when Jon decides to upgrade the wl drivers. Those drivers appear to be proprietary,Broadcom closed source, hence difficult to debug.
  15. szfong

    szfong Network Guru Member

    Hi Pharma,

    It's not people's imaginations that they see their routers spontaneously reboot under Tomato. I've seen the flashing reboot lights and the disconnected icon on more than a couple of occasions . Even though all of my Linksys has a so called "QC Passed" sticker on the main board, it doesn't mean squat. Oftentimes, even chips/board of the same batch will have varying degrees of quality. Thats why even the exact same revision chip&board will have different overclocking abilities and varying levels of signal strength. Newer drivers just seem to have sturdier code which can take into account of flaky/buggy hardware, able to reinitialize itself in certain error conditions, rather than forcing itself to reboot. Haven't you wonder why stock firmware do not prominently show its uptime? It does not mean the router has not rebooted itself. I guess it's a lesser of two evils, if the wl driver hadn't triggerred a reboot, the router may have become unusably unstable, resulting in a return to store or warranty service, which eats up company profit. On dd-wrt, for example, the newest wl driver seems to run in a slightly reduced functionality mode for a time (eg. site survey/wds may no longer work) and if you attempt to use them, after a awhile, the wl driver gets re-initialized, returning to its original self without the need for a reboot.

    The openwrt forums has entire threads covering this issue. Even with the updated drivers, I've seen a few Linksys WRT54G's that shows a disconnect, only almost immediately reconnects... Wouldn't you say this is MUCH better than random reboot which takes up to a minute to reconnect?

  16. starbiker99

    starbiker99 Network Guru Member

    Now that I have dropped back to 1.11 it has now been up for 4 days 13 hours. I'm not sure I ever had 1.13 stay up that long. I will keep an eye on this see what happens.
  17. szfong

    szfong Network Guru Member

    Hi, sometimes putting a heatsink on the cpu and switch chip (on older models), you may have better luck. Underclocking is another option on marginal hardware.

  18. apelete

    apelete LI Guru Member

    I think there's a problem with 1.13, that's all.
    I am exactly in the same case: 1.13 = poor uptimes, 1.11 = no problem.
    The real question is "what is causing the reboots in 1.13 ?".
  19. Trel

    Trel LI Guru Member

    I would just like to add that I too was having many problems in 1.13 and reverting to 1.11 fixed all of them.

    I have a topic on it here.
  20. starbiker99

    starbiker99 Network Guru Member

    Now at 9+ days of uptime back on Ver 1.11 but getting the urge to try 1.14.

Share This Page