From mboxrd@z Thu Jan 1 00:00:00 1970 From: don-lartc@isis.compsvcs.com (Don Cohen) Date: Fri, 29 Jun 2001 21:59:40 +0000 Subject: [LARTC] u32 nexthdr problem Message-Id: List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: lartc@vger.kernel.org I'm having trouble with nexthdr. tc filter add dev eth0 protocol ip parent 10:0 prio 1 u32 \ match ip protocol 0x6 0xff match u8 0x02 0x12 at nexthdr+13 flowid 10:3 fails to match my test packets whereas tc filter add dev eth0 protocol ip parent 10:0 prio 1 u32 \ match ip protocol 0x6 0xff match u8 0x02 0x12 at 33 flowid 10:3 does match them. Of course, the second one is really wrong since it means something totally different if your packet contains any IP options (which my test packets do not, of course). Does anyone either see what I'm doing wrong? Anyone else experience the same problems? Anyone know how to fix them? _______________________________________________ LARTC mailing list / LARTC@mailman.ds9a.nl http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/2.4Routing/