LARTC - May 2003 - what''s wrong with the last line ?

tc qdisc del dev eth1 root
tc qdisc add dev eth1 root handle 10: prio bands 6
tc qdisc add dev eth1 parent 10:1 handle 20: bfifo
tc qdisc add dev eth1 parent 10:2 handle 30: bfifo
tc qdisc add dev eth1 parent 10:3 handle 40: bfifo
tc qdisc add dev eth1 parent 10:4 handle 50: bfifo
tc qdisc add dev eth1 parent 10:5 handle 60: bfifo
tc qdisc add dev eth1 parent 10:6 handle 70: bfifo

#  www traffic
tc filter add dev eth1 parent 10: protocol ip prio 1 u32 match ip dport 80  0xff
flowid 10:1
# pop3 traffic
tc filter add dev eth1 parent 10: protocol ip prio 1 u32 match ip dport 110 
0xff flowid 10:1
# smtp traffic
tc filter add dev eth1 parent 10: protocol ip prio 1 u32 match ip dport 25  0xff
flowid 10:1

#       BANDA 2

# 2234 , 5534  -slsk
tc filter add dev eth1 parent 10: protocol ip prio 2 u32 match ip dport 2234 
0xff flowid 10:2
tc filter add dev eth1 parent 10: protocol ip prio 2 u32 match ip dport 5534 
0xff flowid 10:2
tc filter add dev eth1 parent 10: protocol ip prio 2 u32 match ip sport 2234 
0xff flowid 10:2
tc filter add dev eth1 parent 10: protocol ip prio 2 u32 match ip sport 5534 
0xff flowid 10:2


#   BANDA  3
# yahoo messanger
tc filter add dev eth1 parent 10: protocol ip prio 3 u32 match ip dst
216.136.224.0/24 flowid 10:3
# msn
tc filter add dev eth1 parent 10: protocol ip prio 3 u32 match ip dst
207.46.104.20 flowid 10:3
tc filter add dev eth1 parent 10: protocol ip prio 3 u32 match ip dst
207.46.106.0/24 flowid 10:3
# irc
tc filter add dev eth1 parent 10: protocol ip prio 3 u32 match ip dport 6666
0xff flowid 10:3
tc filter add dev eth1 parent 10: protocol ip prio 3 u32 match ip dport 6667
0xff flowid 10:3



# BANDA  4  -   dcc , kazza , etc...
# unused yet , because I have to dig a little to find out KAZZA''s ports


# BANDA 5  -  cs
tc filter add dev eth1 parent 10: protocol ip prio 5 u32 match ip dport 27015 
0xff flowid 10:5


# the rest of the traffic , not matched by any rule
tc filter add dev eth1 parent 10: protocol ip prio 6 flowid 10:6





when executing the script , it''s all ok , until the last line , when
it''s says:
    "Unknown filter "flowid", hence option "10:6" is
unparsable"


what''s wrong ?  I''ve looked on how-to and seems to be ok..

> # the rest of the traffic , not matched by any rule
> tc filter add dev eth1 parent 10: protocol ip prio 6 flowid 10:6
>
> when executing the script , it''s all ok , until the last line ,
when it''s
> says: "Unknown filter "flowid", hence option
"10:6" is unparsable"
>
> what''s wrong ?  I''ve looked on how-to and seems to be
ok..
You have to specify the filter you want to add : fw, u32 or so.  And the 
options you want.

Stef

-- 

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

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