bytelimit match (traffic shaping)
Tue, 27 Nov 2001 16:12:17 +0100
On Thu, Nov 22, 2001 at 10:20:12AM +0100, firstname.lastname@example.org wrote:
> >> I would really appreciate some feedback ; we use this
> >> bytelimit match here on a router to control the bandwidth
> >> of a high traffic web server, and it runs fine
> > well, I think it's a neat idea, but I thought that was already in the kernel
> > for some time? QoS and TOS combined with the tc and ip tools from the
> > iproute2 package allow you to manage different 'bandwidths' for different
> > applications.
> sure. but the tc+ip method requires to define a queuing discipline,
> a filter to match the traffic, and a tree of classes ; altough there
> are some documentations about the way it works, I found it way
> overkill for most applications - and good documentation explaining
> precisely the meaning of all parameters is hard to find (read :
> sometimes yet-to-be-written). most of the time, I found myself
> tagging the traffic with iptables, and then using tc+ip ; with my
> bytefilter match, I just have to tag the traffic, and can get rid
> of tc+ip.
you can just read the examples from the Linux Advanced Routing HOWTO,
available at www.ds9a.nl.
And: using the MARK target you can combine the powers of iptables matching
and tc/ip QoS features.
> CBQ and the rest of the QoS support is important, but when all you
> want to do is a plain and simple bandwidth limit, it's far easier
> to use bytelimit match.
well, nonetheless not an argument to replicate already existing functionality.
> Jerome Petazzoni <email@example.com>
Live long and prosper
- Harald Welte / firstname.lastname@example.org http://www.gnumonks.org/
GCS/E/IT d- s-: a-- C+++ UL++++$ P+++ L++++$ E--- W- N++ o? K- w--- O- M-
V-- PS+ PE-- Y+ PGP++ t++ 5-- !X !R tv-- b+++ DI? !D G+ e* h+ r% y+(*)