Official Tomato v1.19 released


Automatic rebooting can sometimes be prevented by flashing with the "ND" release.

-Simon
 
failed to access /etc/resolv.dnsmasq: No such file or directory

This message is in my log . I run Tomato 1.19 on wrt54gl v1.1, on other with Tomato_1.16.1374VPN-SDMMC is :
Purko cron.notice crond[94]: crond 1.9.1 started, log level 9
Jan 1 02:00:13 Purko daemon.info dnsmasq[104]: started, version 2.41 cachesize 150
Jan 1 02:00:13 Purko daemon.info dnsmasq[104]: compile time options: no-IPv6 GNU-getopt no-RTC no-ISC-leasefile no-DBus no-I18N no-TFTP
Jan 1 02:00:13 Purko daemon.info dnsmasq[104]: DHCP, IP range 192.168.99.100 -- 192.168.99.149, lease time 1d
Jan 1 02:00:13 Purko daemon.info dnsmasq[104]: reading /etc/resolv.dnsmasq
Jan 1 02:00:13 Purko daemon.info dnsmasq[104]: using nameserver 208.67.220.220#53
Jan 1 02:00:13 Purko daemon.info dnsmasq[104]: using nameserver 212.39.90.43#53
Jan 1 02:00:13 Purko daemon.info dnsmasq[104]: using nameserver 212.39.90.42#53
Jan 1 02:00:13 Purko daemon.info dnsmasq[104]: read /etc/hosts - 0 addresses
Jan 1 02:00:13 Purko daemon.info dnsmasq[104]: read /etc/hosts.dnsmasq - 5 addresses
Jan 1 02:00:13 Purko daemon.crit dnsmasq[89]: failed to bind DHCP server socket: Address already in use
Jan 1 02:00:13 Purko daemon.crit dnsmasq[89]: FAILED to start up

Any ideas ?!?!
 
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.
 
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.

I can add, that sometimes when I watch the real-time bandwidth graph, it comes with a 10 second timeout, like on the screenshot in this link:

http://sitecenter.dk/~jensg/nss-folder/billeder/tomato_log_080510_1155.jpg
 
Installed on a GL and working with it as a client. EXCELLENT! GOOD JOB INDEED! :wave:


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 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 think my stability problems got solved by resetting the NVRAM and entering all my settings again. I hadn't done that for ages.
 
I wonder about the dns caching sometimes.. I have a bunch of DNS servers defined with a 2k cache, and I activated all-servers option too so as to go with the fastest one everytime, and this helped, but still, once in awhile I get a long delay of 'looking up google' or whatever and I can't tell if it's the OS using SRV queries, the web browser, or the router itself.
 
24 days of uptime since my upgrade to 1.19 and no problems. Rock solid wireless too. I think I'll be sticking with this version for a long time to come. Nice work Jon! Thanks.
 
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.
 
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.

I suggest using pfifo. It really improved qos on my wrt54gl. after doing further research, pfifo is the most responsive, and it uses less cpu (hardc0re already pointed that out). I was also getting "Rusty's brain broke!" errors, and only when I removed my l7 filters did they go away. pfifo really helps if you have a lot of connections. I had ~5000 connections for p2p and everything remained responsive (as long as http is classified higher than your p2p connections). sfq (default) doesn't work as well for lots of p2p connections.

Another thing that causes stalls for me weak wireless signal, which happens at different times of the day (i don't know if you are on wireless).
 
I'll look at it. Is this another one that needs to be done via telnet or can we pop it in the script section and try it easily? Not that telnet is all that hard. Its just a lot easier to clear in the script section if you don't want to use it. Also I'm not using qos. Does that matter?

Right now it seems Cox is partly responsible. Something going on with a server out here in the west.
 
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......
 
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......

you only have to set qos_pfifo once. Then it gets saved to nvram. i ssh into my router, but the admin script should work fine.
 
Since I was in the thing via telnet anyway to setup the wan to lan thing I went ahead and did the qos thing. Hard to measure the difference but pages most certainly load faster.
 
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.

Pfifo will definitely be faster than SFQ for large numbers of connections (for example, P2P usage). From what I can see in the source code of the SFQ qdisc, each qdisc only has about 1000 flow / connection queues, so it isn't going to be effective if you have many more connections than 1000 per qdisc level (normally, 1 qdisc level = 1 QOS priority level).

Also if you like even snappier response even with many connections, try my SpeedMod version here. The latest build is pretty much optimized now. :)
 

Back
Top