From: bert hubert <ahu@ds9a.nl>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] tc: u32 match in nexthdr not working?
Date: Fri, 14 Dec 2001 13:32:43 +0000 [thread overview]
Message-ID: <marc-lartc-100833683401739@msgid-missing> (raw)
In-Reply-To: <marc-lartc-100827285418750@msgid-missing>
On Fri, Dec 14, 2001 at 03:15:43PM +0200, Julian Anastasov wrote:
> > Damn, that's broken. Or at least, extremely non-obvious and hard to get
> > working. Overly universal comes to mind. So 'ip sport' would stop matching
> > packets with ip options?
>
> No, ihl includes the options. Everything works perfectly.
> It is bug to use sport and dport if ip options are present. There
Geh. Or an 'undocumented feature'. Because you don't know what kind of
packets you will send or forward, using 'ip sport' is always a bug.
> are tcp dst and tcp src for example. Same for udp. For icmp there
> are icmp type and icmp code. All they use the same base pointer.
But tcp src only works when operating in a hashed filter? Which is
not often the case.
I tried this:
tc filter add dev eth0 parent 1:0 prio 5 u32 \
match ip nofrag \
offset mask 0x0F00 shift 6 \
match tcp src 22 0xffff classid 1:2
But it doesn't work, gives:
RTNETLINK answers: Invalid argument
Regards,
bert
--
http://www.PowerDNS.com Versatile DNS Software & Services
Trilab The Technology People
Netherlabs BV / Rent-a-Nerd.nl - Nerd Available -
'SYN! .. SYN|ACK! .. ACK!' - the mating call of the internet
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/lartc/
next prev parent reply other threads:[~2001-12-14 13:32 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-13 19:46 [LARTC] tc: u32 match in nexthdr not working? Lutz Pressler
2001-12-14 0:13 ` bert hubert
2001-12-14 7:36 ` Lutz Pressler
2001-12-14 12:10 ` Lutz Pressler
2001-12-14 12:56 ` Julian Anastasov
2001-12-14 12:58 ` bert hubert
2001-12-14 13:15 ` Julian Anastasov
2001-12-14 13:32 ` bert hubert [this message]
2001-12-14 13:54 ` Julian Anastasov
2001-12-14 15:16 ` Henrik Nordstrom
2001-12-14 19:59 ` Michael T. Babcock
2001-12-14 23:00 ` bert hubert
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=marc-lartc-100833683401739@msgid-missing \
--to=ahu@ds9a.nl \
--cc=lartc@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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.