From: Marc Schiffbauer <marc.schiffbauer@links2linux.de>
To: LKML <linux-kernel@vger.kernel.org>
Subject: ingress policing still not working in 2.4?
Date: Sat, 9 Feb 2002 12:45:29 +0100 [thread overview]
Message-ID: <20020209114529.GA6753@links2linux.de> (raw)
Hi all,
Is ingress policing not working in the current Kernel?
I'm using the Script from the Advanced Routing HOWTO
(Thanks for that BTW!)
While trying to do a
# tc qdisc add dev ppp0 handle ffff: ingress
I get this:
RTNETLINK answers: No such file or directory
Before that I successfully did this:
# install root CBQ
DEV=ppp0
UPLINK=100
DOWNLINK=750
tc qdisc add dev $DEV root handle 1: cbq avpkt 1000 bandwidth 100mbit
tc class add dev $DEV parent 1: classid 1:1 cbq rate ${UPLINK}kbit \
allot 1500 prio 5 bounded isolated
tc class add dev $DEV parent 1:1 classid 1:10 cbq rate ${UPLINK}kbit \
allot 1600 prio 1 avpkt 1000
tc class add dev $DEV parent 1:1 classid 1:20 cbq rate $[9*$UPLINK/10]kbit \
allot 1600 prio 2 avpkt 1000
tc qdisc add dev $DEV parent 1:10 handle 10: sfq perturb 10
tc qdisc add dev $DEV parent 1:20 handle 20: sfq perturb 10
tc filter add dev $DEV parent 1:0 protocol ip prio 10 u32 \
match ip tos 0x10 0xff flowid 1:10
tc filter add dev $DEV parent 1:0 protocol ip prio 11 u32 \
match ip protocol 1 0xff flowid 1:10
tc filter add dev $DEV parent 1: protocol ip prio 12 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 1:10
tc filter add dev $DEV parent 1: protocol ip prio 13 u32 \
match ip dst 0.0.0.0/0 flowid 1:20
I have crawled the archives and found some mails describing this
problem but I did not find any solution. Some of the mails were
from year 2000...
So does anybody know a solution for that Problem?
I'm using Kernel 2.4.17 with everything <M>'ed or [*]'ed in
QoS-Setup.
The Docu says something about the module would be called cls_ingress.o
but there is only sch_ingress.o. Is this a Docu-Bug BTW?
All sch_* modules seem to load perfectly.
regards
-Marc
--
BUGS My programs never have bugs. They just develop random
features. If you discover such a feature and you want it to
be removed: please send an email to bug@links2linux.de
next reply other threads:[~2002-02-09 11:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-09 11:45 Marc Schiffbauer [this message]
2002-02-09 23:56 ` ingress policing still not working in 2.4? bert hubert
2002-02-10 8:55 ` Marc Schiffbauer
2002-02-10 11:11 ` bert hubert
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=20020209114529.GA6753@links2linux.de \
--to=marc.schiffbauer@links2linux.de \
--cc=linux-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.