That's a good place to start on traffic shaping concepts in general.
In m0n0wall, just remember that a Pipe defines a virtual device capable of
the throughput you define. It will limit all traffic passed through it to
the maximum amount it is capable according to it's definition.
A Queue is a way to prioritize traffic as you send it into a Pipe, so that
important stuff get's a guaranteed amount of bandwidth should the Pipe ever
You should still read the article I linked though, it will help you get a
good idea on how traffic shaping should be implemented to be most effective.
And remember, never shape traffic that you've already recieved from a high
cost link (like your internet provider). All you will ever accomplish is a
lot of packet retransmits, which will eat up even more of your available
bandwidth, which can potentially cause a cascade effect where hardly
anything ever gets through.
Oh, and m0n0wall defines a Pipe size by kbits, not bytes, so a value of 56
is the same as a 56k dialup modem (if you ignore the fcc reg to only
broadcast at no more than 52k over a telephone line, and you ignore stop
bits, and it's your birthday, and the moons are in alignment).
Hope that helps.
----- Original Message -----
From: "Ryan Mullins" <rmullins at ciscomonkey dot net>
To: <m0n0wall at lists dot m0n0 dot ch>
Sent: Tuesday, April 06, 2004 6:20 PM
Subject: [m0n0wall] Traffic Shaping
Does anyone have a good how-to or any good resources on traffic shaping
with m0n0wall they could point me to?