Had some troubles with my router rebooted automatic with 1.17. Like every 3-4 days. Now I have uptime 6 days, 05:31:24 since the 1.19 update. Looking good. Router WRT54G version 2
Me too. 1.19 has also been up 6 days. Looking good!
Had some troubles with my router rebooted automatic with 1.17. Like every 3-4 days. Now I have uptime 6 days, 05:31:24 since the 1.19 update. Looking good. Router WRT54G version 2
I am experiencing some stability problems with my Linksys WRT54GS v1.0, using Tomato v1.19.1463.
Twice it has re-booted, and today it stopped responding in periods after 6 days uptime. I re-booted it, and it seems to work again.
I have been using Tomato since nov or dec 2006, and has never experienced anything like this in the previous versions. My record was more than 70 days with one of the early versions.
Installed on a GL and working with it as a client. EXCELLENT! GOOD JOB INDEED! :wave:
I am experiencing some stability problems with my Linksys WRT54GS v1.0, using Tomato v1.19.1463.
Twice it has re-booted, and today it stopped responding in periods after 6 days uptime. I re-booted it, and it seems to work again.
Please advice: what should be the script for a WRT54GL+Tomato, client to another WRT (router), to light (white) the SES button when a connection exists? Based on ''ping''-ing the gateway, I don't know...suggestions?
I'm having page load lags/stalls with 1.19 as well as victek's mod of 1.19. Gone back to 1.17 and no problems, everything is snappy. Have a Buffalo 54HP for primary router.
Especially on www.avsforum.com with 1.19. Lots of ads/banners that load is seperate windows. With 1.19 it was almost unbearable. Checked with the forum and their end was fine. Could be me and something coincedental of course as Cox is having issues. But the 1.17 firmware does not seem to have any problems.
Originally Posted by hardc0re
No problem. BTW there is a hidden setting in Tomato 1.18 and 1.19, that allows you to switch the QOS qdiscs from SFQ to PFIFO.
#nvram set qos_pfifo=1
#nvram commit
Reboot or restart QoS to make it take effect.
Well it seems to be working by putting it in the script area in Admin. It is most definetly faster. AVS Forum loads as quick as I can ever remember it. I mean snaps right up there.
I'll have to read back and see what it is I'm actually doing......
The commands to switch QOS qdiscs from sfq to pfifo need to be done only once. Just telnet in, enter commands, nvram commit, reboot. You don't need to put it in the startup script.Well it seems to be working by putting it in the script area in Admin. It is most definetly faster. AVS Forum loads as quick as I can ever remember it. I mean snaps right up there.
I'll have to read back and see what it is I'm actually doing......
We use essential cookies to make this site work, and optional cookies to enhance your experience.