Re: [LARTC] filters not doing anything?

Linux Advanced Routing and Traffic Control

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Monday 21 April 2003 16:04, Frank v Waveren wrote:
> On Mon, Apr 21, 2003 at 11:20:12AM +0200, Stef Coene wrote:
> > And try this if you want to have a catch all rule :
> > tc filter add dev eth0 parent 1: protocol ip u32 match ip src 0/0 flowid
> > 2:1
>
> Tried that too, the packets still aren't going through the SFQ.
>
> The setup:
> BW=80
> DEV=eth1
>
> HBW=$(($BW/2))
>
> tc qdisc del dev $DEV root
> tc qdisc add dev $DEV root handle 1: htb r2q 1
> tc class add dev $DEV parent 1: classid 1:1 htb rate ${BW}kbit ceil
> ${BW}kbit tc qdisc add dev $DEV parent 1:1 handle 2: prio bands 4
> tc qdisc add dev $DEV parent 2:1 handle 10: sfq perturb 10 # Lowlatency
> tc qdisc add dev $DEV parent 2:2 handle 20: sfq perturb 10 # Medium Latency
> tc qdisc add dev $DEV parent 2:3 handle 30: sfq perturb 10 # Regular
> tc qdisc add dev $DEV parent 2:4 handle 40: htb r2q 1      # Bulk
>
> tc class add dev $DEV parent 40: classid 40:1 htb rate ${HBW}kbit ceil
> ${BW}kbit tc class add dev $DEV parent 40: classid 40:2 htb rate ${HBW}kbit
> ceil ${BW}kbit tc qdisc add dev $DEV parent 40:1 handle 41: sfq perturb 10
> tc qdisc add dev $DEV parent 40:2 handle 42: sfq perturb 10
>
> tc filter add dev $DEV parent 1: protocol ip prio 1 u32 match ip protocol 1
> 0xff flowid 2:1 tc filter add dev $DEV parent 1: protocol ip prio 1 u32
> match ip tos 0x10 0xff flowid 2:1 tc filter add dev $DEV parent 1: protocol
> ip prio 1 u32 match ip protocol 6 0xff match u8 0x05 0x0f at 0 match u16
> 0x0000 0xffc0 at 2 match u8 0x10 0xff at 33 flowid 2:1 # Small ACKs
>
> tc filter add dev $DEV parent 1: protocol ip prio 2 handle 1022 fw flowid
> 40:1  # Bulk1 tc filter add dev $DEV parent 1: protocol ip prio 2 handle
> 1027 fw flowid 40:2  # Bulk2
>
> tc filter add dev $DEV parent 1: protocol ip prio 3 u32 match ip protocol 6
> 0xff match u8 0x10 0xff at nexthdr+13 flowid 2:1  # All ACKs
>
> tc filter add dev $DEV protocol ip parent 1: prio 999 u32 match ip src 0/0
> flowid 2:3  # Anything else goes into the Regular category
But where is your catch all rule to put the packets in the 2:4 band?
And you never put packets in the 2:2 band.

An other question, why do you added that 4 bands prio?  You can do the same 
only with the htb qdisc.

Stef

-- 

stef.coene@xxxxxxxxx
 "Using Linux as bandwidth manager"
     http://www.docum.org/
     #lartc @ irc.oftc.net



[Index of Archives]     [LARTC Home Page]     [Netfilter]     [Netfilter Development]     [Network Development]     [Bugtraq]     [GCC Help]     [Yosemite News]     [Linux Kernel]     [Fedora Users]
  Powered by Linux