who uses tomato firmware?

headstrong

Expert Member
Joined
May 10, 2006
Messages
1,099
Reaction score
0
Hi

Does any1 use tomato firmware?
I am considering upgrading from dd-wrt v23sp2 to tomato firmware on my wrt54gl....

I would just like an opinion on tomato firmware before I do something stupid :)
1) Is it reliably?
2) is it safe to flash from dd-wrt?
3) is it stable?
4) does it have high packet loss?

Thanks alot
 
Hi

Does any1 use tomato firmware?
I am considering upgrading from dd-wrt v23sp2 to tomato firmware on my wrt54gl....

I would just like an opinion on tomato firmware before I do something stupid :)
1) Is it reliably?
2) is it safe to flash from dd-wrt?
3) is it stable?
4) does it have high packet loss?

Thanks alot

there is nothing wrong with dd-wrt....

I have 4 dd-wrt's, havent had any problems with them sofar, so im sticking to dd-wrt

Packet loss isnt caused by the firmware, not dd-wrt atleast.
 
The only thing I like about Tomato firmware is the Source - Tomato source

It all depends on what you want to do. Why change if the current firmware is working for you.
 
Tomato Me!

Tomato firmware is Excellent.

Firmware: http://www.polarcloud.com/tomato
Wikibook: http://en.wikibooks.org/wiki/Tomato_Firmware
Forums: http://www.linksysinfo.org/forums/forumdisplay.php?f=160

Some reasons:
1) It's based most closely on the official WRT GPL releases from Linksys
2) It's got the most informative and intuitive user interface by far
3) It has excellent built-in QoS functionality and configurability with live graphs (Just be careful not to add too many rules, the Linksys CPU is not THAT powerful!)
4) Interactive user interface and Eye candy! SVG graphs list current and historic throughputs; Device list shows WDS and Client signal strengths.
5) No idiotic grammar or spelling in UI; Pages do not disappear unneccesarily while reloading/submitting settings
6) It is not coded by a german weed freak with purple hair begging for money, but by the author of Tofu/Thibor firmware, one with a reputation to be the fastest and most stable.

While I've had DD-WRT fail on me multiple times, I've not had issues with Tomato.

You can upgrade from DD-WRT. Just do a
nvram show | grep pass
To see what the login password will be. But a hard reset will (hold reset button for 30 seconds right after boot), of course, reset it! And get rid of all the junk put in nvram by DD-WRT. (Also, have you had a look at all the redundant firewall rules that DD-WRT adds by default?! Its such a hack!)

It's first boot takes about a minute, so don't get impatient.

You can also upgrade it via ssh:

Code:
mypc# dd if=/tomato/WRT54G/code.bin of=/mywebserver/code.trx bs=32 skip=1
...
mypc# md5sum /mywebserver/code.trx
123xxxxxxxxxxxxxxxxxxxxx456 
mypc# ssh tomatome
tomatome# wget [url]http://mypc.mynet/code.trx[/url]
...
tomatome# md5sum code.trx
123xxxxxxxxxxxxxxxxxxxxx456  
tomatome# mtd-write -i code.trx -d linux
...
tomatome# reboot

Next step would be to make cocktail tomatoes... :D ... (make it run on the Atheros platform devices... that's what I'm working on ;))
 
Last edited:
Hi

4) does it have high packet loss?

Thanks alot

If you aim to maximise your packet loss, I would suggest you broadcast on the most highly occupied channel, and boost your output power to anything over 120mW and try to get your RSSI below -91dBm. Good luck!
 
Last edited:
Hi

1) Is it reliably?
3) is it stable?

Thanks alot

1) YES
3) NO

Err.. Maybe that was 1) NO 3) Yes

:confused:

:eek: YES!!!!!! :eek:

Although, I do have one point that keeps failing after about 6-7 days of uptime. But it did that in DD too, so it must be the hardware or something deeper in the firmware (This particular one runs in B-only mode and only takes connections from Prism devices.)

Note that the WRT's are very peculiar about their power. If you give too little they crash. Some Cat5 has a lot of resistance. I've run one of my WRT's from 3.5V right up to 40V. The caps on the board are only rated 25V though.
 
Ok I successfully flashed my 4 wrt54gl's with tomato v1.06 without a problem!

I however have one problem with the WDS link:



................................................D(AP + WDS)
...................................................... |
...................................................... | (WDS link)
...................................................... |
...................................................... |

A( ethernet bridge)----wifi---->B( Central AP + WDS)------wifi----->C(ethernet bridge)

The WDS link goes down every 20 hrs and I need to phone a friend to reboot router B via his ethernet bridge...This fixes the problem but costs me a phone call every day!

Can I make wrt54gl running tomato firmware to auto reboot every day at a certain time?

Or how can i fex down WDS links?

Thanks
 
Almost sure it's not tomato related.... But, you can just find your cron spool....

cd /
find | grep cron

and add

* 4 * * * /sbin/reboot

If you think it will solve the problem... at 4am each morning.

Hmm.. Not sure if that will stay across reboots. Probably not!

better try the built-in cron tool:

cru a DailyRestart "0 4 * * * reboot"

(Just double check...)

Have you monitored the signal strengths? Are they poor? Tried a different channel?

What firmware did you have before? Did you do a complete reset of each router, or did you just flash them and leave the settings intact? (Bad idea- never know how (in)compatible the previous firmware settings could be...)

Try the wiki... or the tomato forums... Keep us posted!
 
Last edited:
Hi Tunasashimi

I previously had dd-wrt v23 sp2...

I think that the problom resided in my channel selection. I had it on channel 11 by default so I changed it to a different channel

I havnt had a problem but it has only been up for about 24 hours or so.

Please ellaborate on the Daily restart thing.... I will do a google aswell

Thanks
 
Last edited:
How do I set the time in tomato?

I have set the the ntp server to "pool.ntp.org"

Tomato shows that the time is unavailable...

Can I hard code the time somehow?
 
Top
Sign up to the MyBroadband newsletter
X