Re: [LARTC] filters not doing anything?

[Frank v Waveren <fvw.lartc@var.cx>]

On Mon, Apr 21, 2003 at 09:33:52PM +0200, Stef Coene wrote:
> > The setup:
> > BW€
> > 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?
Catchall rule? I only want fwmarked traffic in 2:4, and it gets in
there through 40:1 and 40:2.

> And you never put packets in the 2:2 band.
Yeah, that's yet to be filled, I was going to select traffic for that
once I had it up and running. But I don't yes, because I can't even
get the simple test case working properly, let alone this :-(

> An other question, why do you added that 4 bands prio?  You can do the same 
> only with the htb qdisc.
How? I want the first band to have priority, always. I could make its
rate equal to its ceil, but that'd mean the other classes in the HTB
would have to have rate 0, and that'd mean the bandwidth that gets
left after the first band was depleted would get distributed evenly,
and I don't want that.

-- 
Frank v Waveren                                      Fingerprint: 21A7 C7F3
fvw@[var.cx|stack.nl|chello.nl] ICQ#10074100            1FF3 47FF 545C CB53
Public key: hkp://wwwkeys.pgp.net/fvw@var.cx            7BD9 09C0 3AC1 6DF2
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/