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

v1.21 unstable?

Discussion in 'Tomato Firmware' started by SirDracula, Sep 28, 2008.

  1. SirDracula

    SirDracula Network Guru Member

    I moved from Thibor to Tomato v1.21 during the DNS scare, on a WRT54GS v3.

    Every few days the router just reboots. Thibor was rock solid, uptime for months.

    I don't run anything special on the router, just your typical configuration, WAN, a couple of wired and a couple of wireless clients. When it's up, it's great, but it's annoying to lose my ssh and VPN tunnels every few days.

    Anyone else seeing the same thing? Any suggestions how to narrow down the problem? I did a n nvram clean when I installed Tomato and entered all settings by hand so old configs from Thibor can't be it. I also haven't seen any newer Tomato versions, does that mean 1.21 is stable or the developer has lost interest in it?

  2. fyellin

    fyellin LI Guru Member

    Very strange. Most users seem to be finding v1.21 to be quite solid. My router was up for about 30 days straight until we got a power outage. And this included dozens of wired and wireless clients.

    You're not doing anything unusual?
  3. SirDracula

    SirDracula Network Guru Member

    Nothing unusual that was not already set up with Thibor, not even any bt traffic. I have another Buffalo router running the same v1.21 and it's running in wireless client mode, connected to the Linksys AP. The Buffalo has been up 57 days, but the Linksys can barely stay up for 3-4 days. I'd love to at least find out which component is crashing it. I've been monitoring the memory consumption and it doesn't seem to be going up, so it's something else that triggers a complete reboot.
  4. Trunkz

    Trunkz LI Guru Member

    This might sound daft, but when you moved from Thibor to Tomato, did you clear the NVRAM? If you hadnt, thats probably the case. You should always wipe the nvram clean after each upgrade of tomato, nevermind from a different distribution altogether.
  5. Toastman

    Toastman Super Moderator Staff Member Member

    This may not be relevant but...

    The wireless driver in Tomato is known to cause the router to reboot when certain wireless clients connect, mostly the Intel 2200B/G. I have heard that Thibor 15c never did this, I don't know if it used a more stable driver (I didn't know there was one at that time). If you search this forum there are many articles about the problem.

    Is one of your clients using an Intel wireless card? Just a thought...
  6. Mastec

    Mastec Network Guru Member

    Version 1.21 wireless is very stable. Clear the nvram again and reflash. My 3 routers run on 1.21 and have never had a complaint from any wireless client that they were disconnected.
  7. SirDracula

    SirDracula Network Guru Member

    Hmm ... that is very strange. Yes, one of my clients is an Intel 3945ABG.

    To the other replies, yes, I cleaned nvram after I installed Tomato a few times.
  8. szfong

    szfong Network Guru Member

    Try Tomato 1.21 ND on it. Although it's a trx, you can flash it just the same.

  9. SirDracula

    SirDracula Network Guru Member

    ND seems to be for Buffalo WHR-G125 according to the Tomato site. I have a WRT54GS v3 which I don't want to brick. They don't make them anymore and I've grown rather attached to it over the past 4+ years :)
  10. szfong

    szfong Network Guru Member

    I use Tomato ND on a WRT54G v2, a bcm4712-based router. Only the Measure Noise floor causes it to lose wireless momentarily. I have the boot_wait enabled in the bootloader and enabled easy recovery if bricked by overclocking according to the openwrt instructions. And have backups of the bootloader for jtag recovery if needed. I've never needed jtag on this router though. Anyhow, all firmware upgrades come w/ some risk. You have several options... The old Thirbor15c, Tomato ND, or dd-wrt v24 post sp1 TNG (vintage and NEWD) are options I've tested and appears to fix this particular issue.

    Good Luck

  11. SirDracula

    SirDracula Network Guru Member

    Could having WPA2/WPA enabled have anything to do with it? I switched to having only WPA with AES enabled for now to see how it goes. I can't use WPA2 anyway because client mode doesn't work with WPA2.
  12. likuidkewl

    likuidkewl Network Guru Member

    I also noted frequent lockups of the router with 1.21, this has never happened before.
    I too have a 3945 wireless card using wpa2/wpa.

    I am running linux most of the time, but I noticed Windows exhibits the same behavior on occasion. Its like the AP just plain out locks.
  13. SirDracula

    SirDracula Network Guru Member

    Speaking of Linux, I noticed that on a laptop with a Broadcom wireless N internal card, running Ubuntu with the NDIS wrapper the router with Tomato 1.21 crashes more often when this said client tries to associate (and it takes a long time to associate). Didn't notice the problem when running Windows XP on the same client. Regardless, a wireless client should not be able to crash a router and I understand that the Broadcom drivers that Tomato uses are closed source and there isn't much they can do about it.
  14. nobugme

    nobugme Network Guru Registered

    i have the same/similar problem

    my WRT54GL will just freeze randomly, like, the connection stays, but i cant access the router ip or any external websites, even if i replug my ethernet, will get my xx.xx.xx.111 ip which i assigned, so i know the router isnt ENTIRELY frozen

    and yeah, it has rebooted randomly before, not anymore that i notice, the freezing seems to have replaced it
  15. SirDracula

    SirDracula Network Guru Member

    Disabling WPA2 made no difference, the router still reboots every few days ...
  16. Sunspark

    Sunspark LI Guru Member

    I have a WRT54GL 1.1 revC.

    Today, I flashed in build 1544 of Tomato 1.21 ND for the first time ever!

    What motivated me to do so, was the fact that last night once again (this happens every month, or longer) the laptop lost connection to the router, and I could not reconnect to it, and it was rejecting my password, etc. Yet the ethernet portion continued to work just fine. Even after a power cycle the problem continued so I just let it sit for an hour and it fixed itself.

    Other than that, which I think has been present in all versions, Tomato 1.21 has been quite stable.
  17. Toastman

    Toastman Super Moderator Staff Member Member

    Seems pretty obvious it is the Intel cards.

    The ND driver does work for the 54GL, as you can see from Sunspark's post. But the big problem with the ND driver is that while it cures the reboot problem, it unfortunately introduces another - namely, that many Intel cards will no longer be able to associate.

    The latest versions of the driver cure all of the problems, but can't be included in Tomato yet, because it uses an earlier version of the Linux kernel. DD-WRT has upgraded and uses a newer wireless driver - I use it on my AP's, but stick with tomato on the router.

    Here's a link to some relevant stuff we were discussing a while back in a different thread:

  18. Sunspark

    Sunspark LI Guru Member

    Would you happen to know offhand the technical challenges inherent in upgrading the kernel so that it can take advantage of the newer 4.170 drivers?
  19. likuidkewl

    likuidkewl Network Guru Member

    I stand corrected from my previous statement:
    root@None:~# uname -a
    Linux None 2.4.36 #308 Sun Jul 27 16:11:05 CEST 2008 mips unknown
  20. SirDracula

    SirDracula Network Guru Member

    If DD-WRT is more stable, which version should I put on my WRT54GS v3? I need the minimal amount of features, I don't use anything fancy like QoS, VPN, hence I want the simplest version to configure without a lot of bloatware in it. Features I really need from a stock firmware are stability and static DHCP.
  21. Toastman

    Toastman Super Moderator Staff Member Member

    Look for one for your model router with the smallest filesize, usually will have a name like mini * nokaid.*
  22. likuidkewl

    likuidkewl Network Guru Member

    I have to say I switched to DD-WRT 24_SP1. All is going well for now we will see how it holds up.
  23. SirDracula

    SirDracula Network Guru Member

    FWIW, I got fed up with the repeated reboots so I switched to DD-WRT v24sp1 mini. We'll see how that goes, so far so good and the network "feels" faster so far.

    I still have Tomato v1.21 on a Buffalo router in client bridge mode and I will keep it like that as that router has been up for almost 31 days now.
  24. geoffc

    geoffc Addicted to LI Member

    I'm still running 1.19 with no problems.

    /tmp/home/root # uptime
     21:23:43 up 57 days, 16:14, load average: 0.04, 0.02, 0.00
  25. likuidkewl

    likuidkewl Network Guru Member

    I have to say DD-WRT has already long out lived my 1.21 stability record(over 3 weeks now).
    It really bothered me to switch, but I am now seeing the benefits.
    Also, DD-WRT seems to do a better job managing the antennas as I used to have problems with coverage, even cranked to 150mw, now at a mere 100mw I get full coverage with over a 65% signal @ 54mbs. Fantastic!
    I may try 1.22 if/when it comes out but this is looking to be less and less likely every day.
  26. Mastec

    Mastec Network Guru Member

    Uptime since firmware adjustment

    Attached Files:

  27. Toastman

    Toastman Super Moderator Staff Member Member

    I'm curious, does anyone know why Thibor 15C would not give the same problems with Intel cards as later firmwares? Has it been confirmed by any investigation that it really did not have problems? (I've searched, but not found any evidence one way or another).

    to Likuidkewl - I switched to DD-WRT on my AP's a few months ago now. But all still up and no reboots due to my 20 - odd Intel users.

    Just for fun, as one of the AP's is connected to a spare ASDSL line (2nd gateway) - I tried using it for all our internet traffic to see if other areas of DD-WRT had improved. But the QOS is still awful and it could not handle it well.

    One thing I did like, was the greatly improved latency for games which was reported by several users. This was, I believe, due to TCP Vegas. However, without proper QOS it was still of no use in my particular environment.
  28. leonash07

    leonash07 Guest

    I'm up for 70 days since I last install Mod 1.21. Internet and connection is good. I do loose internet connection on my wireless laptop, however if I disable and enable my connection on my laptop connection is back to normal. Not sure if router or my laptop issue. All other stuff is normal. I don't use setting like CIFS and JIFF2 as I have no use for it for my internet setting.

    Attached Files:

  29. likuidkewl

    likuidkewl Network Guru Member

    @Toastman: As this is for my home network we don't much worry about QOS so I cannot comment on that. But I can say that I would see a needed reboot every 3-4 days before with my Thinkpad being the only Intel wireless. But it was not the only wireless going down, my S/O's wireless would also bite it if I tried to connect and ended up with a fail, then when she would try it would say it couldn't find the AP any longer. Almost like the Wireless interface would crash(she uses a RT2500 based card with Mint).
    At work it is a completely different story, we are running 3 Tomato WRT54GL's in AP mode and have had no issues. But, we have no intel wireless cards in the Dells they are all Broadcoms. I guess I don't bring mine in enough to make it crash. Soon we will be running some more WRT54GL's in another location with Tomato in a place that sees more frequent intel wireless, so we will see if it can be replicated.
  30. SirDracula

    SirDracula Network Guru Member

    DD-WRT has been stable for over 1 week, I could not get more than 2-3 days out of Tomato 1.21 without a reboot.
  31. Toastman

    Toastman Super Moderator Staff Member Member

    Seems like 3 days is about average for Tomato in the sites I maintain. I used to be a real critic of DD-RT but now I think it has improved somewhat. I do wish the team would pay attention to the horrible QOS though.

    I have more information now on the Intel users here than I had before. Actually most of the cards are not 2200BG, they are the 3945. But I have to smile ... about half of the laptops that had these cards (HP, Compaq models) have overheated and burned out, so the problem is gradually disappearing.

    I am so glad I never bought one :)
  32. likuidkewl

    likuidkewl Network Guru Member

    I also have a 3945 in the Thinkpad.
    That is one way to "fix it" :)

    FYI - I had a Compaq that lasted for 3.5 years so don't count your blessings yet!
  33. Toastman

    Toastman Super Moderator Staff Member Member

    A week ago I went for a walk around the Seri center - a local large department store with a floor devoted to IT and Computers. One repair shop had a lot of cardboard boxes on the floor with bargain items in - so I walked in to look for bargains. Across the back of the shop was a steel rack where customers repairs etc. were being kept. One section of it had literally hundreds of laptops stacked up high, being cannibalised for spares. It was sad to see so many quite recent HP/Compaq computers in there, probably not long out of warranty.
  34. likuidkewl

    likuidkewl Network Guru Member

    How is 1.22 fairing in this regard?

Share This Page