From: Stef Coene <stef.coene@docum.org>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] tc filter problem with 2.4.22
Date: Thu, 16 Oct 2003 17:31:40 +0000 [thread overview]
Message-ID: <marc-lartc-106632676415642@msgid-missing> (raw)
In-Reply-To: <marc-lartc-106632466912820@msgid-missing>
On Thursday 16 October 2003 18:50, Andrzej Szymanski wrote:
> Hi,
>
> I have a problem with 'tc filter' on a 2.4.22 kernel from Slackware 9.1
> distribution.
> The tc command binary is from htb3.6-020525.tgz
> (http://luxik.cdi.cz/~devik/qos/htb)
>
> I'm trying the following command sequence:
>
> tc qdisc add dev eth0 root handle 1: htb default 1 r2q 1
> tc class add dev eth0 parent 1: classid 1:1 htb rate 1200kbit ceil
> 1200kbit
> tc class add dev eth0 parent 1:1 classid 1:1002 htb rate 20kbit ceil
> 1200kbit burst 1600 cburst 1600
> tc qdisc add dev eth0 handle 1002 parent 1:1002 sfq perturb 10
> tc filter add dev eth0 protocol ip parent 1:0 prio 10 u32 match ip src
> 10.0.0.2 flowid 1:1002
>
> 'tc filter' command returns:
> RTNETLINK answers: Invalid argument
>
> moreover, 'tc filter show' returns:
> RTNETLINK answers: Invalid argument
> Dump terminated
>
> Everything worked OK on another linux with older (2.4.20) kernel.
>
> Do you have an idea what's wrong?
Mhh. I have a tc binary on www.docum.org, can you try that one?
http://www.docum.org/stef.coene/qos/download/
Stef
--
stef.coene@docum.org
"Using Linux as bandwidth manager"
http://www.docum.org/
#lartc @ irc.openprojects.net
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next prev parent reply other threads:[~2003-10-16 17:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-16 16:50 [LARTC] tc filter problem with 2.4.22 Andrzej Szymanski
2003-10-16 17:31 ` Stef Coene [this message]
2003-10-16 17:42 ` Andrzej Szymanski
2003-10-16 17:48 ` Stef Coene
2003-10-16 18:20 ` Andrzej Szymanski
2003-10-17 15:40 ` Damjan
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-106632676415642@msgid-missing \
--to=stef.coene@docum.org \
--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