If eth0 is your interface connected to the Internet, shape outgoing traffic on eth1. This will simulate the effect of limiting download coming thro' eth0 and also shape traffic from the local machine going out to the LAN on eth1. In case you want to limit download from the local machines to nodes on eth0 and eth1, apply QoS on both interfaces. Bridging does not affect or help this in any way. Ethernet interfaces do not need to have IP addresses for QoS to be applied in Linux. I've used htb-init with bridge-nf which has been documented in the LEAF Bering user manual. In case you have any questions, I'll be glad to answer them as the maintainer of that part of the documentation. HTH. Warm regards Mohan > -----Original Message----- > From: lartc-admin@xxxxxxxxxxxxxxx > [mailto:lartc-admin@xxxxxxxxxxxxxxx] On Behalf Of Ed Wildgoose > Sent: Wednesday, June 16, 2004 9:23 PM > To: lartc@xxxxxxxxxxxxxxx > Subject: QOS Script difficulty on bridge > > I'm playing with the rather excellent QOS script from > Alexander Clouter at http://digriz.org.uk/jdg-qos-script/ > > So far I am really impressed with it - a very impressive > example of the power of linux QOS rules (has pretty much > everything in it from the LARTC Howto!) However, the > instructions hint that "for QoS to affect locally generated > traffic in a non ethernet bridge setup you must have IMQ". > > Now, I *DO* have a bridged config (br -> eth0 & eth1), but I > can't see how I can set things up so that traffic from the > local machine suffers the effect of the QOS limitations (on > download) without using IMQ. > > More broadly, can *anyone* see how it might be possible to > limit the download rate to a local machine running as a > bridge, without using IMQ? > (err, and not using the policer either, I want an HTB qdisk > running on the download traffic - I just want to know if I am > missing something obvious about the way the bridge works) > > Just for reference only the bridge has an ip address, both > physical interfaces are anonymous. > > Thanks for any pointers. > > Ed W > > P.S. Anyone using this script on 2.6 with a bridge needs to > be aware that the syntax for "tc" has changed. You can't use > "tc -i eth0" > anymore, you need "tc -i br0 -m physdev --physdev-in eth0". > And the same for "-o". Hope that helps anyone who tries the > script out > > _______________________________________________ > LARTC mailing list / LARTC@xxxxxxxxxxxxxxx > http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: > http://lartc.org/ _______________________________________________ LARTC mailing list / LARTC@xxxxxxxxxxxxxxx http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
