From: DervishD <lartc@dervishd.net>
Date: Fri, 25 Nov 2005 16:44:19 +0000
Subject: [LARTC] [RESEND] tc filter: match tcp src vs. match ip sport
Message-Id: <20051125164419.GB199@DervishD>
List-Id: <lartc.vger.kernel.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
To: lartc@vger.kernel.org

    Hi all :))

    Sorry for asking again, but got no answers and google doesn't
give useful information (seems like "nexthdr" doesn't work right, but
I don't know why...). I really want to know what am I doing wrong...
=20
    This filter matches what I want:
=20
    tc filter add dev eth0 protocol ip parent 1:0 prio 9 u32\
            match ip sport 0x3000 0xf000 flowid 1:22
=20
    and traffic goes to 1:22, but this one doesn't match:

    tc filter add dev eth0 protocol ip parent 1:0 prio 9 u32\
            match tcp src 0x3000 0xf000 flowid 1:22
=20
    I don't understand why the first one matches and the second one
doesn't :? because in the output of "tc filter show" the only
difference is that the first one matches "at 20" and the second one
"at nexthdr+0", which should be identical :?????

    Looks like "nexthdr" is not working, and I prefer to use it just
in case I have to filter IP packets with options (because then the
first filter won't work).
=20
    What the heck am I doing wrong? Is iptables my only option?
What's the matter with "nexthdr"?

    Thanks a lot in advance :)

    Ra=FAl N=FA=F1ez de Arenas Coronado

--=20
Linux Registered User 88736 | http://www.dervishd.net
http://www.pleyades.net & http://www.gotesdelluna.net
It's my PC and I'll cry if I want to...
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc