* [LARTC] RTNETLINK answers: Invalid argument, fwmark
@ 2002-07-26 16:24 David Watson
2002-07-26 17:39 ` Stef Coene
2002-07-30 10:19 ` David Watson
0 siblings, 2 replies; 3+ messages in thread
From: David Watson @ 2002-07-26 16:24 UTC (permalink / raw)
To: lartc
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.
_____________________________________________________________
David Watson, Network Manager, Team17 Software Ltd.
Phone: +44-1924-267776 Fax: +44-1924-267658
_____________________________________________________________
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [LARTC] RTNETLINK answers: Invalid argument, fwmark
2002-07-26 16:24 [LARTC] RTNETLINK answers: Invalid argument, fwmark David Watson
@ 2002-07-26 17:39 ` Stef Coene
2002-07-30 10:19 ` David Watson
1 sibling, 0 replies; 3+ messages in thread
From: Stef Coene @ 2002-07-26 17:39 UTC (permalink / raw)
To: lartc
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/
^ permalink raw reply [flat|nested] 3+ messages in thread* Re: [LARTC] RTNETLINK answers: Invalid argument, fwmark
2002-07-26 16:24 [LARTC] RTNETLINK answers: Invalid argument, fwmark David Watson
2002-07-26 17:39 ` Stef Coene
@ 2002-07-30 10:19 ` David Watson
1 sibling, 0 replies; 3+ messages in thread
From: David Watson @ 2002-07-30 10:19 UTC (permalink / raw)
To: lartc
I missed a line in my report and I do in fact create a 1:1 class
before attaching to it. I have found that if I change the prio value on the
filter lines to unique numbers that I no longer get the error. I am however
confused as to the meaning of the prio parameter, and I'm not sure why
these filter lines need unique values or exactly what impact these values have.
At 19:39 26/07/2002 +0200, Stef Coene wrote:
>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/
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2002-07-30 10:19 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2002-07-26 16:24 [LARTC] RTNETLINK answers: Invalid argument, fwmark David Watson
2002-07-26 17:39 ` Stef Coene
2002-07-30 10:19 ` David Watson
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.