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:
signature.asc
Description: This is a digitally signed message part
