Quote:
Originally Posted by rds_correia
Hmmm, Karl buddy I'm afraid I don't quite understand those readings.
I mean, I don't even know how much bandwidth you're getting on your current wi-fi connection (*cough*) I mean DSL connection.
And then the bottom graph.
I really don't know what to make of it.
I mean it must be good otherwise you wouldn't be posting it but I'd like to understand it so that I can compare it with mine.
Can you help me understand it better?
Cheers
|
Ok
The top graph shows the bandwidth on a 5 hour windows.
The bottom pie charts shows bandwidth consumption per class. That is, the percentage allocated to different services, like VoIP.
In my case, I have VoIP set to "Highest", so when anyone picks up a phone at home, you would see the "Highest" segment on the pie chart the largest piece.
Like this:
Compare that to the previous pie chart (the bottom one), and you'll see on the color chart where the "Highest" is the largest piece on the pie. That's while I was on the phone.
So basically "Tomato" (the firmware
) dynamically allocates bandwidth to services, and I can even be running file sharing apps and what not, and voice sessions are not choppy or interrupted
Also Tomato does layer 7 (L7) filtering, so you can "class" just about any program without knowing what ports it uses. Sort of like Snort's stateful packet inspection.
This is a VERY powerful feature of this firmware.
Say I want to run Bittorrent, but I'm not sure if anyone on another machine in a LAN has it set up to use non-standard ports.
I would do this:
And that puts anyone on a low priority bucket, regardless of what port they are trying to use
Read more about it here:
http://l7-filter.sourceforge.net/
-kwag