Hi Ryan. I see that uve done a pretty good job using only TC as a bandwidth shapper. Can i ask u a favor? Could u send me an exemple of shapping 4 different IP addresses with four different speeds. EX: 10.0.0.15 = 256kbps 10.0.0.16 = 384kbps 10.0.0.17 = 512kbps 10.0.0.18 = 768kbps is that a way to shappe inbound speed different than the outbound speed using TC? if that is, could u send me an example script too? thanks a lot. Cristian ----- Original Message ----- From: "Ryan Rothert" <ryan@xxxxxxxxxxx> To: "For users of Fedora Core releases" <fedora-list@xxxxxxxxxx> Sent: Friday, March 26, 2004 6:18 PM Subject: bridge and tc bandwith management > > Hello, > > I finally got iptables to work with my bridge using the kernel from arjanv's > page (2.6.3-2.1.253.2.1) ... Im trying to now get tc to work so I can shape > some traffic. When I enter the following commands , there are no errors, > however the tc rules are having no effect on the IP im trying to shape. > > I just want to limit IP 10.0.0.17 to 512k, and 10.0.0.18 to 1024k and so > on, Here are my tc rules > > DEV=eth0 > tc qdisc del dev $DEV root > tc qdisc add dev $DEV root handle 1: cbq avpkt 1000 bandwidth 100mbit > tc class add dev $DEV parent 1: classid 1:1 cbq rate 512kbit allot 1500 prio > 5 bounded isolated > tc filter add dev $DEV parent 1: protocol ip prio 16 u32 match ip dst > 10.0.0.17 flowid 1:1 > tc filter add dev $DEV parent 1: protocol ip prio 16 u32 match ip src > 10.0.0.17 flowid 1:1 > > > eth0 is internal interface ---\ > |------br0 (I gave br0 an IP just > for management) > eth1 is external interface---/ > > Any thoughts on why this doesnt work ? I have used these same rules on > another Fedora box that acts as a NAT/router and that worked fine, > but this new box has to act has a bridge. > > Thanks, > Ryan > > > > > > -- > fedora-list mailing list > fedora-list@xxxxxxxxxx > To unsubscribe: http://www.redhat.com/mailman/listinfo/fedora-list > >
