Which version for WRT54GL

Discussion in 'Tomato Firmware' started by krneki, Jun 2, 2014.

  1. krneki

    krneki Networkin' Nut Member

    Currently I have "1.28.7634 Toastman-IPT-ND ND VPN" installed on my WRT54GL, but I find it somehow unstable because it often drops wi-fi connection for 10 seconds and then comes up again.

    Could you please advice me on which version/build of Tomato should I try?
  2. Porter

    Porter LI Guru Member

    I used this version without the VPN for almost a year and had no trouble. Toastman is one of the most stable firmwares around, so it would be difficult to find something better.

    Which of the settings did you change?
    Are you sure it's the router and not a connected device?
    Can you reproduce that behaviour or is it seemingly arbitrary?
    How stable is the stock firmware, did you try that?
  3. krneki

    krneki Networkin' Nut Member

    Settings: only wireless security, SSID name, QoS and port forwarding
    I'm sure it's router since it drops all connected clients. Actually it won't even show up in available Wireless Networks for ~10 seconds.
    It seems to be completely random.
    I haven't tried stock yet.
  4. Porter

    Porter LI Guru Member

    Does the router reboot or is it somehow limited to the wifi? You can check this in the GUI under Status/Overview.

    Just to throw it out there: There always is the possibility of a real hardware defect.
  5. EOC_Jason

    EOC_Jason LI Guru Member

    Try resetting your router back to default settings (do the thorough clear NVRAM) and slowly reconfigure & test it. See if you can re-create the problem or possibly track it down to a particular module (like QOS or VPN)...

    There isn't too much development / support for the old 2.4 kernel based routers...

    The good news is you can get a LOT newer N based router on eBay for like $30 or less... People are always upgrading to the latest models or their ISP's router includes wifi so they sell off what they have.
  6. Porter

    Porter LI Guru Member

    In terms of wifi reliability there probably isn't anything better than the old WRT54GLs. Their driver is working really well and there is a reason why they easily reach uptimes for over a year. Forthermore Toastman always says that those newer drivers can be more or less unstable.

    Let me give you an example: I recently bought a Asus RT-N16 and flashed a recent Toastman build. Whenever I try to use Bittorrent Sync in my internal network, the router crashes within 2 to 30 minutes. No idea what's going wrong, but it's clearly related to wifi traffic. Doing the same things trough my old WRT54GL is no problem.
  7. krneki

    krneki Networkin' Nut Member

    Here, this is right after Wi-Fi connection dropped (I've turned router physically off and on few hours ago):

    Model Linksys WRT54G/GS/GL
    Chipset Broadcom BCM5352 chip rev 0 pkg 2
    CPU Freq 200 MHz
    Flash RAM Size 4 MB

    Time Mon, 02 Jun 2014 23:23:45 +0200
    Uptime 0 days, 00:00:59
    CPU Load (1 / 5 / 15 mins) 1.43 / 0.41 / 0.14
    CPU Usage 88.55%
    Total / Free Memory 14.04 MB / 5,860.00 KB (40.77%)

    Status Connected
    Connection Uptime 0 days, 00:01:04
    Remaining Lease Time 29 days, 23:58:56
  8. Porter

    Porter LI Guru Member

    The uptime was just 59 seconds, so it seems like your router reboots and therefore actually crashes.

    Resetting the NVRAM might help. Also check that you are _not_ using QoS and the bandwidth limiter at the same time.
  9. EOC_Jason

    EOC_Jason LI Guru Member

    I'm not dogging those old routers, I still have a WRT54GS that runs like a champ. I gave my suggestion to try and reset the router settings back to defaults and ensure that its running stable then slowly reconfigure it to see if you can track down what the issue is.

    If you can find out exactly what the cause (and hopefully solution) is, then you can probably get toastman to roll out an update. But otherwise I was saying don't expect any updates for the router "just because", like I said they are old models and most developers have focused their energy on the newer models that have better support (with faster processors, newer wireless, more flash, more ram, etc...)
  10. Marcel Tunks

    Marcel Tunks Networkin' Nut Member

    CPU load was pretty high. Another approach to what EOC_Jason said would be to disable any features you don't need, such as ethernet port states, UPnP, VPN, Web/bandwidth/ip traffic monitoring, QoS, BW limiter. Which of these features are you using? What is your bandwidth from the ISP? You can also consider overclock to 250MHz at a very small risk of bricking or worse stability if you insist on flogging that little CPU ;-)
  11. mpegmaster

    mpegmaster Addicted to LI Member

    OR... could it be the signs of a flaky power supply!:cool:
  12. krneki

    krneki Networkin' Nut Member

    Actually QoS wasn't enabled at all, only bandwidth limiter. I haven't resetted NVRAM yet, but I found out that it helps a lot if I close uTorrent. Basically I haven't had any problems so far since I've disabled uTorrent.
  13. Porter

    Porter LI Guru Member

    Yeah, uTorrent... That's a very special case. I've had problems with it myself, but the router never rebooted itself, although it had a load of ~6! ;)

    You could try this:
    1. Limit the number of concurrent connections to 1000 under Advanced/Conntrack/Netfilter.
    2. What kills the router are UDP-connections because although uTorrent says it limits its connections, it only does this for TCP. UDP traffic is completeley out of control! So I recommend to change the UDP Timeouts on the same page. I recommend Unreplied=30 and Assured=90. This should still be high enough so you don't run into problems.
    3. Somewhere on this forum Toastman posted some information about limiting your conurrent connections per IP address with iptables. This might be another idea, if you have other devices on your network and need some fairness so that nobody can hog all the connections.
  14. abubin

    abubin Addicted to LI Member

    maybe you can try go to conntrack/netfilter -> connections increase it to 8192. I think default if 4096. This will allow double the connection tracking which helps a lot when using torrent.
  15. Porter

    Porter LI Guru Member

    No, he should not increase the amount of concurrent connections. I have tested this. My WRT54GL couldn't handle more than 1000 connections because of RAM limitations.
  16. EOC_Jason

    EOC_Jason LI Guru Member

    Disabling DHT also helps if you don't need it... That will create a lot of connections that you may or may not be using.
  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.
    Dismiss Notice