For Mike,
After setting up a bridge interface, there is an appropriate entry in
the table returned by 'ip link show' for br0 (or whatever you called
your bridging interface.
So.. it looks like it will work ;-) and that you can add a QoS
queueing discipline in the same manner as as any other interface.
# tc qdisc add dev br0 root cbq
# (etc.)
A question for the developers. Once the eth0,eth1 interfaces have been
bound to br0, is any queuing discipline attached to them still used?
I have an application of QoS where I would like to bridge between two
100BaseTX interfaces, one of which ends up going to an ADSL link
(eth0).
eth0 eth1
--[ ADSL Router] ------[ Bridge ]------[ Local Subnet ]
br0
The options are:
- Adding a single 'cbq' to br0 which distinquishes between traffic
going out on eth0 and eth1 (via through destination
address). Traffic going directly to the router would have a local
subnet address, and so it would be classified as 'eth1' traffic
and receive appropriate treatment. (This may not be such a bad thing.)
- (If it works?) Adding QoS queueing disciplines to 'eth0' and
'eth1' directly. This would only work if these get called when the
packet gets sent out on the appropriate interface.
I suspect that this second option would be faster, as the QoS
policy used is effectivly chosen at 'routing' time, rather than
having to go through a second decision making process. (Speed and
delay could be an issue in some cases like VoIP connections, but
not having done any work on this yet, I can't say..)
Comments?
> On Wed, Jan 09, 2002 at 11:46:10PM -0700, Mike wrote:
>
> > Do QOS and fair queueing work with bridging?
>
> Yes. Why don't you try?
>
> cheers,
> Lennert
_______________________________________________
Bridge mailing list
[EMAIL PROTECTED]
http://www.math.leidenuniv.nl/mailman/listinfo/bridge
