[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/functions.php on line 4752: Cannot modify header information - headers already sent by (output started at [ROOT]/includes/functions.php:3887)
[phpBB Debug] PHP Warning: in file [ROOT]/includes/functions.php on line 4754: Cannot modify header information - headers already sent by (output started at [ROOT]/includes/functions.php:3887)
[phpBB Debug] PHP Warning: in file [ROOT]/includes/functions.php on line 4755: Cannot modify header information - headers already sent by (output started at [ROOT]/includes/functions.php:3887)
[phpBB Debug] PHP Warning: in file [ROOT]/includes/functions.php on line 4756: Cannot modify header information - headers already sent by (output started at [ROOT]/includes/functions.php:3887)
FTA-N-More.Net • View topic - dd-wrt vs Tomato
Login    Forum    Search    FAQ     Radio

Board index » WiFi Zone » WiFi Discussions




Post new topic Reply to topic  [ 3 posts ] 
Author Message
 Post subject: dd-wrt vs Tomato
 Post Posted: Tue Jul 20, 2010 7:29 pm 
Offline
EVEN MORE OF A Contributing Member
User avatar

Joined: Mon Apr 26, 2010 6:53 pm
Posts: 119
Let me start with explaining what dd-wrt is. It is a firmware for supported hardware routers to increase the number of features you can get out of your $30+ router easily turning it into having the same features and capabilities as a $600 router. Some prominent features include Kai Daemon for the Kai Console Gaming network, WDS wireless bridging/repeating protocol, Radius Authentication for more secure wireless communication, advanced Quality of Service controls for bandwidth allocation, and software support for the SD-Card hardware modification.

I have extensively used dd-wrt for a fairly long period of time. More precisely I would put it in between somewhere 2-3 years. The last version that I had used was dd-wrt v24 Special Edition SP1. I really had no complaints. My router a Linksys WRT54-GL v1.1 remained stable even at the highest usage times. There were rarely any crashes. It made my router extremely secure, especially with options such as using https protocol to log onto the router, option to limit logging into the router as admin only via ethernet connection, hence disabling any traffic sniffer to be able to log on to your router via wireless connection and changing access levels to his/her liking.

But what brought about my interest in Tomato was when I was searching for a way to record the logs to an external mySQL server through rflow. I got rflow working to the point where it was receiving all the netflow information and showing it to me in a nice graph or list view.

I feel rflow is too hyped up to be more than what it is. I wish there were tools more extensive that could use the information being sent through the router and elegantly show number of bytes being used by a connection, activity being performed on the connection and henceforth. Maybe rflow does have that option somewhere in there and I just haven’t been patient enough to look for it. Regardless I still feel there is a need for a better netflow software tool for the routers.

Whilst searching for a more robust netflow tool for my router I came across Tomato. The reviews were off the chart. The most prominent difference what I can feel, sense, observe is the faster connection speeds I am experiencing. Webpages are loading much more faster, and QOS is working like the way it should.

The setup was really easy, even moving up from a dd-wrt to a Tomoto firmware was seamless. It didn’t break anything. I found the layout of the configuration page so much more refreshing and far less overwhelming. The graphs are a pleasant addition to the whole firmware, where they show you different options such as real-time monitoring, last 24 hours, daily, weekly and monthly options.
The QOS on this firmware is just amazing. I have 2 laptops running vuze downloads, watching YouTube, browsing the Internet, chatting on MSN Messenger and everything is running without a hiccup. No single laptop is sucking up all the bandwidth, the router is distributing the requests efficiently and effortlessly.
In all honesty at the time of this writing (06/23/2009): I have only had the router running for less tha 72 hours. But the last 72 hours have proven to be promising. I think I am going to indefinitely stick to Tomato until the next better firmware comes around.

On a side note I still haven’t found a netflow software to my liking that would work with Tomato.

Update (06/23/2010): It has now been almost 12 months since my installation of Tomato and its still going strong with ZERO hiccups. I have never had to worry about resetting the router.


Top 
 Profile  
 
 Post subject: If you like Tomato
 Post Posted: Tue Jul 20, 2010 7:40 pm 
Offline
EVEN MORE OF A Contributing Member
User avatar

Joined: Mon Apr 26, 2010 6:53 pm
Posts: 119
If you like Tomato, you should try Victek's RAF version as well. IMO it is even better/faster than stock Tomato as it's optimized for high p2p load.

http://victek.is-a-geek.com/

http://www.linksysinfo.org/forums/showthread.php?...


Top 
 Profile  
 
 Post subject: Re: dd-wrt vs Tomato
 Post Posted: Tue Jul 20, 2010 7:48 pm 
Offline
SUPER USER
User avatar

Joined: Fri Apr 09, 2010 11:07 pm
Posts: 645
Location: Boonies
Tomato is best if you ISP supports MLPPP or Multy link point to point, which allows you to bypass throttleing m if needed ;)

_________________
Admit Nothing, Deny EVERYTHING, DEMAND Pr00f!


Top 
 Profile  
 
Display posts from previous:  Sort by  
 
Post new topic Reply to topic  [ 3 posts ] 

Board index » WiFi Zone » WiFi Discussions


Who is online

Users browsing this forum: No registered users and 1 guest

 
 

 
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Search for:
Jump to:  
cron