* [LARTC] fw and match filters (was NAT+mangle+tc)
@ 2004-10-12 23:29 Ethy H. Brito
2004-10-13 5:38 ` Robert Felber
0 siblings, 1 reply; 2+ messages in thread
From: Ethy H. Brito @ 2004-10-12 23:29 UTC (permalink / raw)
To: lartc
On Tue, 12 Oct 2004, Robert Felber wrote:
> try:
>
> tc filter add dev eth2 protocol ip parent 1: prio 1 handle 1 fw classid 1:X
>
> X is your class, it should not be 1 since this is usually a root class (I
> guess you are using HTB). Example:
Ok. I created two special classes under '1:' for each interface to acomodate
the icmp traffic.
Now the 'tc filter ... fw ... ' lines works flawlessly.
But after I execute the 'tc filter ... fw ... ' command, every
'tc filter ... match ... ' after those gives me the
'RTNETLINK answers: Invalid argument' error.
Aren't they (fw and match) supposed to cohexist?
If I comment the 2 'filter fw' lines the errors desappear.
Any ideas?
Ethy H. Brito /"\
InterNexo Ltda. \ / CAMPANHA DA FITA ASCII - CONTRA MAIL HTML
+55 (12) 3941-6860 X ASCII RIBBON CAMPAIGN - AGAINST HTML MAIL
S.J.Campos - Brasil / \
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: [LARTC] fw and match filters (was NAT+mangle+tc)
2004-10-12 23:29 [LARTC] fw and match filters (was NAT+mangle+tc) Ethy H. Brito
@ 2004-10-13 5:38 ` Robert Felber
0 siblings, 0 replies; 2+ messages in thread
From: Robert Felber @ 2004-10-13 5:38 UTC (permalink / raw)
To: lartc
[-- Attachment #1: Type: text/plain, Size: 1359 bytes --]
On Wed, 2004-10-13 at 01:29, Ethy H. Brito wrote:
> Ok. I created two special classes under '1:' for each interface to acomodate
> the icmp traffic.
> Now the 'tc filter ... fw ... ' lines works flawlessly.
>
> But after I execute the 'tc filter ... fw ... ' command, every
> 'tc filter ... match ... ' after those gives me the
> 'RTNETLINK answers: Invalid argument' error.
>
> Aren't they (fw and match) supposed to cohexist?
Hm, no. I have a setup based soley on fw-marks. After adding an u32
match filter i get no RTNETLINK messages:
# tc filter show dev imq0
filter parent 1: protocol ip pref 1 fw
filter parent 1: protocol ip pref 1 fw handle 0x1 classid 1:10
filter parent 1: protocol ip pref 2 fw
filter parent 1: protocol ip pref 2 fw handle 0x2 classid 1:20
filter parent 1: protocol ip pref 10 u32
filter parent 1: protocol ip pref 10 u32 fh 800: ht divisor 1
filter parent 1: protocol ip pref 10 u32 fh 800::800 order 2048 key
ht 800 bkt 0 flowid 1:30
match 312c0404/ffffffff at 12
probably some version bug? I have
# tc -V
tc utility, iproute2-ss020116
--
Robert Felber (EDV-Leitung)
Autohaus Erich Kuttendreier
Drosselweg 21
81827 Muenchen
Tel: +49 (0) 89 / 453 12-86
Fax: +49 (0) 89 / 453 12-80
PGP: 896CF30B
PGP-Fingerprint: CF36 AA93 9716 63E8 962F 15CC A80E 1A79 BF77 25EA
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 187 bytes --]
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2004-10-13 5:38 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2004-10-12 23:29 [LARTC] fw and match filters (was NAT+mangle+tc) Ethy H. Brito
2004-10-13 5:38 ` Robert Felber
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.