Re: [LARTC] Bandwidth throttling/limiting for all traffic

[Darryl Cording <dcording@ascend.net.au>]

Darryl Cording wrote:
>>
>> Right, because it wasn't classified.
>>
> Ok, so I have to classify my traffic before this will route them throu 
> the qdisc. Are you taking about classifying via iptables?? I thought 
> that was optional, more for filtering ...etc.
> 
> regards
> darryl
> 
I was getting confused with the terminology. I was thinking filtering 
was meaning something else when "tc filter ..." actually does the 
classifying. I was also assuming that if you don't specify any packet 
attributes to filter on it would just catch everything, seems it's the 
opposite.

OK, so I used this;

tc qdisc add dev eth0 root handle 10: htb default 10
tc class add dev eth0 parent 10: classid 10:1 htb rate 64kbit ceil 64kbit
   and have been experimenting with classifying like this,
tc filter add dev eth0 parent 10: protocol ip prio 1 u32 match ip 
protocol 0 0xff
tc filter add dev eth0 parent 10: protocol ip prio 1 u32 match ip 
protocol 6 0xff

But it seems my ftp transfers are not being shaped, in fact, lol, they 
are going faster from when I first started experimenting. So it's not 
matching correctly. I just want to shape everything going past the 
NIC's. I thought that if I could classify the entire ip protocol or the 
tcp protocol that would shape the bulk of the traffic ?  I was hoping 
not having to get down to specifying ports, but find a simple way to 
shape all outgoing traffic on a multi-homed host.

Am I on the right track?

And what worries me also now, is that the application traffic coming 
over the wire will be DCOM, which I think is rpc based, another world of 
hurt if I have to figure out what ports that app is using.

thanks for any tips,
darryl



_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/