Linux Advanced Routing and Traffic Control list
 help / color / mirror / Atom feed
From: Bartek Krajnik <bartek@bicom.pl>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] tc filter question
Date: Fri, 14 Feb 2003 15:09:23 +0000	[thread overview]
Message-ID: <marc-lartc-104523545211437@msgid-missing> (raw)
In-Reply-To: <marc-lartc-104521804622882@msgid-missing>

[-- Attachment #1: Type: text/plain, Size: 908 bytes --]

On 14-02-2003 at 11:19:10AM +0100, philipp.berndt@gmx.net wrote:
> Hello.
> 
> I tried this:
> 
> $ ./tc qdisc add dev ppp0 root handle 1:0 htb default 12
> $ ./tc class add dev ppp0 parent 1:0 classid 1:1 htb rate 125kbit ceil 125kbit
> $ ./tc class add dev ppp0 parent 1:1 classid 1:10 htb rate 10kbit ceil 125kbit 
> prio 0
> 
> $ iptables .... -j MARK --set-mark 11
> 
> $ ./tc filter add dev ppp0 parent 1:0 prio 0 protocol ip handle 10 fw flowid 
> 1:10
> RTNETLINK answers: Invalid argument
> 
> Can anybody tell me what's wrong with the last line?
> 
> I tried it with tc from
> http://luxik.cdi.cz/~devik/qos/htb/v3/htb3.6-020525.tgz
> and from iproute2-2.4.7-340.rpm (SuSE 8.1).
> 
> Do I need some other kernel module?
Recompile Your kernel with option CONFIG_NET_CLS_FW.
Networking options  --->QoS and/or fair queueing  --->Firewall based classifier

Rgds,
  Bartek.

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2003-02-14 15:09 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-14 10:19 [LARTC] tc filter question philipp.berndt
2003-02-14 15:09 ` Bartek Krajnik [this message]
2003-02-14 16:15 ` Philipp Berndt
2007-10-28 17:48 ` Daniel
2007-10-28 18:55 ` Peter V. Saveliev
2007-10-28 18:56 ` Andreas Mueller
2007-10-29  5:32 ` Michal Soltys
  -- strict thread matches above, loose matches on Subject: below --
2003-06-30 14:42 Σταμάτης Κεκές
2003-06-30 14:50 ` Ethy H. Brito
2003-06-30 15:05 ` ???????? ?????
2003-06-30 15:23 ` Ethy H. Brito
2003-07-01  6:00 ` ???????? ?????

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-104523545211437@msgid-missing \
    --to=bartek@bicom.pl \
    --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