[LARTC] Problems with TC

[LARTC] Problems with TC

[Lars Goldschlager]

Greetings all... I write because i've been battlign a
problem with tc for two days and I can't find a
solution or a response to the failure... Basically I
am trying to shape marked packages since I have a NAT
and I discovered of course that I couldn't shape based
on ip with the NAT in place, for the rule didn't
apply... so I set a mark to the packages depending on
the ip they came from, but then when I try to
implement the filter to match these packages into a
queue rule I get the following error from tc: 
RTNETLINK answers: Invalid argument

The sytnax I am using is the following:
/sbin/tc filter add dev eth0 parent 1:0 protocol ip
prio 1 handle 188 fw flowid 1:3

I've tried diferent syntaxes to no avail, I am
thinking of trying to use an always-matching u32 rule
instead of fw but I do not know if that is possible or
if it'll ever work... also i've checked the kernel and
I seem to have everything I need compiled, anyhow if
someone sends me the list of options I need for this
specific type of filter I can recheck... anyhow
advanced routing is compiled, such as multiple
tables.. and I have cls_fw as a module which loads
correctly into kernel...... Any pointers please???

Thanks a lot.

Lars.

==/|\               /    \
A dragon         ((    ))
a day         /\  \\/\//  /\
lights your  ///\ (o<>o) /\\\
way         /////\ \}{/ /\\\\\
/|\        ////ooO\(oo)/Ooo\\\\
---------------VVV------VVV---------------
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

Re: [LARTC] Problems with TC

[Stef Coene]

On Wednesday 04 June 2003 17:51, Lars Goldschlager wrote:
> Greetings all... I write because i've been battlign a
> problem with tc for two days and I can't find a
> solution or a response to the failure... Basically I
> am trying to shape marked packages since I have a NAT
> and I discovered of course that I couldn't shape based
> on ip with the NAT in place, for the rule didn't
> apply... so I set a mark to the packages depending on
> the ip they came from, but then when I try to
> implement the filter to match these packages into a
> queue rule I get the following error from tc:
> RTNETLINK answers: Invalid argument
>
> The sytnax I am using is the following:
> /sbin/tc filter add dev eth0 parent 1:0 protocol ip
> prio 1 handle 188 fw flowid 1:3
>
> I've tried diferent syntaxes to no avail, I am
> thinking of trying to use an always-matching u32 rule
> instead of fw but I do not know if that is possible or
> if it'll ever work... also i've checked the kernel and
> I seem to have everything I need compiled, anyhow if
> someone sends me the list of options I need for this
> specific type of filter I can recheck... anyhow
> advanced routing is compiled, such as multiple
> tables.. and I have cls_fw as a module which loads
> correctly into kernel...... Any pointers please???
Do you have a class 1:3?  If not, that's why got the error.

Stef

-- 

stef.coene@docum.org
 "Using Linux as bandwidth manager"
     http://www.docum.org/
     #lartc @ irc.oftc.net

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

[LARTC] problems with tc

[Michael P. Soulier]

People,

I'm trying to set up the tc filters for a PRIO queue. I'm basing it off
of marked traffic via iptables. For example, I've marked two classes of
traffic with ids "2" and "4", and now I'm filtering those to bands 1 and
2.

tc filter add dev eth0 parent 1: prio 0 protocol ip \
    handle 2 fw flowid 10:1
tc filter add dev eth0 parent 1: prio 1 protocol ip \
    handle 4 fw flowid 10:2

This works fine, but now I'd like to add a "catch all" rule to send
everything else to band 10:3. According to the Advanced Routing HOWTO,
this should work:

tc filter add dev eth0 parent 1: prio 2 flowid 10:3

But, it doesn't...

Unknown filter "flowid", hence option "10:3" is unparsable

Also, after adding in ingress queue, I can't seem to remove it. 

tc qdisc del dev eth0 ingress

I get: RTNETLINK answers: Invalid argument

This is on an updated RedHat 7.3 box.

[root@sme61a2-1 root]# uname -a
Linux sme61a2-1 2.4.20-18.7 #1 Thu May 29 08:32:50 EDT 2003 i686 unknown
[root@sme61a2-1 root]# rpm -q iproute
iproute-2.4.7-7.80.1

Any help appreciated.

Mike

-- 
Michael P. Soulier <michael_soulier@mitel.com>, 613-592-2122 x2522
6000/6010/60* Development, Mitel Networks Corporation
"...the word HACK is used as a verb to indicate a massive amount of nerd-like
effort." -Harley Hahn, A Student's Guide to Unix
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

Re: [LARTC] problems with tc

[Michael P. Soulier]

On 24/08/04 Michael P. Soulier did say:

> People,
> 
> I'm trying to set up the tc filters for a PRIO queue. I'm basing it off
> of marked traffic via iptables. For example, I've marked two classes of
> traffic with ids "2" and "4", and now I'm filtering those to bands 1 and
> 2.
> 
> tc filter add dev eth0 parent 1: prio 0 protocol ip \
>     handle 2 fw flowid 10:1
> tc filter add dev eth0 parent 1: prio 1 protocol ip \
>     handle 4 fw flowid 10:2
> 
> This works fine, but now I'd like to add a "catch all" rule to send
> everything else to band 10:3. According to the Advanced Routing HOWTO,
> this should work:
> 
> tc filter add dev eth0 parent 1: prio 2 flowid 10:3
> 
> But, it doesn't...
> 
> Unknown filter "flowid", hence option "10:3" is unparsable
> 
> Also, after adding in ingress queue, I can't seem to remove it. 
> 
> tc qdisc del dev eth0 ingress
> 
> I get: RTNETLINK answers: Invalid argument
> 
> This is on an updated RedHat 7.3 box.
> 
> [root@sme61a2-1 root]# uname -a
> Linux sme61a2-1 2.4.20-18.7 #1 Thu May 29 08:32:50 EDT 2003 i686 unknown
> [root@sme61a2-1 root]# rpm -q iproute
> iproute-2.4.7-7.80.1
> 
> Any help appreciated.

So no one knows the answers to these questions? Perhaps the HOWTO should
be updated to reflect the fact that the commands given simply don't
work, or that the implementation is broken with certain kernels/iproute
versions. That would help greatly instead of fumbling in the dark like
this. 

Cheers,
Mike

-- 
Michael P. Soulier <michael_soulier@mitel.com>, 613-592-2122 x2522
6000/6010/60* Development, Mitel Networks Corporation
"...the word HACK is used as a verb to indicate a massive amount of nerd-like
effort." -Harley Hahn, A Student's Guide to Unix
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/