Hi Alexander, On Mon, 28 Feb 2005 19:51:39 +0300 Alexander Kirillov <[EMAIL PROTECTED]> wrote: [quotes re-sorted] > > - use netfilter to route relevant connections through a shaper > > device (which is a - AFAIK - experimental kernel feature, > This netfilter approach you've mentioned. Is it something > different from iptables extensions you have to compile with the > kernel?
Yes, i meant configuring the kernel with support for the connection shaping device, see -> Device Drivers -> Networking support -> Network device support. I just mentioned netfilter because you could use it to mark packets for routing to certain devices. You need to use routing because that traffic shaper appears as a new (virtual) device. > > - use "tc" and the QoS-Kernel-Features. > I don't mind recompiling the kernel and would rather use a generic > tool useful for system administration later down the road. > Looks like tc is the way to go. It gives you a lot of options. It's in the iproute2-package. It has a little high learning curve, but you can do really interesting things and even simulate higher latencies. For a good introduction see the Linux Advanced Routing and Traffic Control HowTo, http://lartc.org You can use netfilter here, too, to mark the relevant packets. HWH -- [email protected] mailing list
