Linux Advanced Routing and Traffic Control list
 help / color / mirror / Atom feed
From: "Alex" <afornieles@free.fr>
To: lartc@vger.kernel.org
Subject: [LARTC] Can't use fwmark filters
Date: Sun, 26 Oct 2003 16:08:30 +0000	[thread overview]
Message-ID: <marc-lartc-106718639420388@msgid-missing> (raw)

Hello,

I'm facing an issue that i have reported on Debian's BTS as a bug against
iproute package. Prior to this i have been looking around trying to find
out what could be wrong but had no success to get it to work.

Below is a what i've reported on Debian's BTS as
http://bugs.debian.org/215629

Here goes the story, thanks for any tip on the subject.

Alex

----

I would like to add a fwmark filter to the original HTB based
LARTC "WonderShaper" script (http://lartc.org/wondershaper/).

I am using a self compiled kernel from latest sarge
kernel-source-2.4.22 and based on kernel-image-2.4.22-k7 provided config
file.

The idea is to add a single additionnal fwmark filter :

tc filter add dev ppp0 parent 1: protocol ip prio 10 \
handle 1 fw classid 1:30

When adding this line i get the following error message :

RTNETLINK answers: Invalid argument

If i modify the WonderShaper script, remove all "tc filter" lines but the
fwmark filter one i get no such error.
The filter seems to get declared just fine.

From here i can start uncommenting some of the "tc filter" lines
provided in WonderShaper without getting any error.
At some point when having enabled again 4 or 5 "tc filter" original
lines the reported error strikes again.

I have tried simplifying the script to something like this :

tc qdisc add dev ppp0 root handle 1: htb default 60

tc class add dev ppp0 parent 1: classid 1:1 htb rate 450kbit
tc class add dev ppp0 parent 1:1 classid 1:10 htb rate 450kbit
tc class add dev ppp0 parent 1:1 classid 1:60 htb rate 450kbit

tc qdisc add dev ppp0 parent 1:10 handle 10: sfq
tc qdisc add dev ppp0 parent 1:60 handle 60: sfq

tc filter add dev ppp0 parent 1: protocol ip prio 1 handle 1 fw classid 1:10
tc filter add dev ppp0 parent 1: protocol ip prio 1 handle 6 fw classid 1:60

Which works fine.

Adding this single line triggers the error again :

tc filter add dev ppp0 parent 1: protocol ip prio 1 u32 \
match ip tos 0x10 0xff  flowid 1:10

---> RTNETLINK answers: Invalid argument


I am stucked here... i haven't been able to find anything related to
this on the net and i hope not to be misusing 'tc'.

Thank you.


-- System Information:
Debian Release: testing/unstable
Architecture: i386
Kernel: Linux routeur 2.4.22-routeur3 #1 Sat Oct 11 11:40:45 CEST 2003 i686
Locale: LANG=C, LC_CTYPE=C

Versions of packages iproute depends on:
ii  libc6                         2.3.2-7    GNU C Library: Shared
libraries an

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

             reply	other threads:[~2003-10-26 16:08 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-26 16:08 Alex [this message]
2003-10-31 20:16 ` [LARTC] Can't use fwmark filters sanyi

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-106718639420388@msgid-missing \
    --to=afornieles@free.fr \
    --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