I use this configuration. You still use eth0 and eth1 and not br0. It works as intended. tc operates at one level below bridging code at the device queue level as I understand it. Thus whether it is a bridge or router, we shape on the physical interface level. I guess like imq (virtual device) some tinkering will need to be done to use br0 as a device on which QoS can be applied. HTH Mohan -----Original Message----- From: lartc-admin@xxxxxxxxxxxxxxx [mailto:lartc-admin@xxxxxxxxxxxxxxx]On Behalf Of Abraham van der Merwe Sent: 04 March 2003 14:29 To: Linux Advanced Routing & Traffic Control list Subject: [LARTC] QoS on bridge device Hi! Usually if you have a machine and traffic passes through it: +-----+ eth0| QoS | -------------| box |------------- | |eth1 +-----+ You can shape outgoing traffic on eth0 and eth1 effectively shaping both incoming/outgoing traffic. With bridging and above setup you only have a single device br0 - my question is whether you can shape both incoming/outgoing traffic on this device (i would presume it is not possible) or do you need to redirect traffic passing through br0 to imq0 and do shaping on outgoing traffic on both br0 and imq0? -- Regards Abraham If you're not part of the solution, you're part of the precipitate. ___________________________________________________ Abraham vd Merwe [ZR1BBQ] - Frogfoot Networks P.O. Box 3472, Matieland, Stellenbosch, 7602 Cell: +27 82 565 4451 Http: http://www.frogfoot.net/ Email: abz@xxxxxxxxxxxx
