From: "Alexandru Coseru" <alexcos@home.ro>
To: lartc@vger.kernel.org
Subject: [LARTC] what's wrong with the last line ?
Date: Sun, 11 May 2003 14:47:07 +0000 [thread overview]
Message-ID: <marc-lartc-105266452907813@msgid-missing> (raw)
[-- Attachment #1: Type: text/plain, Size: 2273 bytes --]
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..
[-- Attachment #2: Type: text/html, Size: 4195 bytes --]
next reply other threads:[~2003-05-11 14:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-11 14:47 Alexandru Coseru [this message]
2003-05-11 20:23 ` [LARTC] what's wrong with the last line ? Stef Coene
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=marc-lartc-105266452907813@msgid-missing \
--to=alexcos@home.ro \
--cc=lartc@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox