From: Stef Coene <stef.coene@docum.org>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] RTNETLINK answers: Invalid argument, fwmark
Date: Fri, 26 Jul 2002 17:39:57 +0000 [thread overview]
Message-ID: <marc-lartc-102770523530043@msgid-missing> (raw)
In-Reply-To: <marc-lartc-102770074124628@msgid-missing>
On Friday 26 July 2002 18:24, David Watson wrote:
> I'm using htb classes on my firewall to queue traffic and implement
> different restrictions on different protocols.
>
> tc qdisc del dev eth0 root
> tc qdisc add dev eth0 root handle 1: htb default 190
> tc class add dev eth0 parent 1: classid 1:3 htb rate 2mbit burst 30k
> tc class add dev eth0 parent 1:1 classid 1:90 htb rate 50kbit ceil 384kbit
> burst 5k
> tc qdisc add dev eth0 parent 1:90 handle 190: sfq perturb 10
> tc qdisc add dev eth0 parent 1:3 handle 310: sfq perturb 10
>
>
> tc filter add dev eth0 protocol ip parent 1:0 prio 1 handle 3 fw flowid 1:3
>
> This last line gets a "RTNETLINK answers: Invalid argument"
>
> I'm using kernel 2.4.18 with the htb and wrr patches on both the kernel and
> on tc
> in the kernel .config I have:
>
> CONFIG_IP_ADVANCED_ROUTER=y
> CONFIG_IP_MULTIPLE_TABLES=y
> CONFIG_IP_ROUTE_FWMARK=y
>
>
> I'm not really sure where else I could be going wrong, any advice would be
> greatly appreciated.
You attach class 1:90 to class 1:1, but you didn't create class 1:1 ??
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:[~2002-07-26 17:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-26 16:24 [LARTC] RTNETLINK answers: Invalid argument, fwmark David Watson
2002-07-26 17:39 ` Stef Coene [this message]
2002-07-30 10:19 ` David Watson
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-102770523530043@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 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.