From: Patrick McHardy <kaber@trash.net>
To: Denys Fedoryshchenko <denys@visp.net.lb>
Cc: netdev@vger.kernel.org,
Stephen Hemminger <shemminger@linux-foundation.org>
Subject: Re: iproute2 / match / meta bug?
Date: Tue, 29 Jul 2008 08:18:26 +0200 [thread overview]
Message-ID: <488EB632.9@trash.net> (raw)
In-Reply-To: <200807290911.35809.denys@visp.net.lb>
Denys Fedoryshchenko wrote:
> Well, the issue not with ifb0 only. It is just not parsing rules correctly i think:
>
> rich tc # ./tc filter add dev ifb0 protocol all basic match meta\(protocol eq 1234\) classid 1:100
> rich tc # ./tc filter add dev ifb0 protocol all basic match meta\(data_len eq 1234\) classid 1:100
>
> filter parent 1: protocol all pref 49151 basic
> filter parent 1: protocol all pref 49151 basic handle 0x1 flowid 1:100
> meta(-1 eq 1234)
>
> filter parent 1: protocol all pref 49152 basic
> filter parent 1: protocol all pref 49152 basic handle 0x1 flowid 1:100
> meta(-1 eq 1234)
>
Works fine here with a fresh git checkout:
# tc filter add dev dummy0 protocol all parent 1: basic match
meta\(protocol eq 1234\) classid 1:100
# tc -s -d filter show dev dummy0
filter parent 1: protocol all pref 49151 basic
filter parent 1: protocol all pref 49151 basic handle 0x1 flowid 1:100
meta(protocol mask 0x00000000 eq 1234)
filter parent 1: protocol all pref 49152 basic
next prev parent reply other threads:[~2008-07-29 6:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-29 5:43 iproute2 / match / meta bug? Denys Fedoryshchenko
2008-07-29 5:54 ` Patrick McHardy
2008-07-29 6:11 ` Denys Fedoryshchenko
2008-07-29 6:18 ` Patrick McHardy [this message]
2008-07-29 6:25 ` Denys Fedoryshchenko
2008-07-29 6:35 ` Denys Fedoryshchenko
2008-07-29 8:16 ` Denys Fedoryshchenko
2008-07-29 6:18 ` Denys Fedoryshchenko
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=488EB632.9@trash.net \
--to=kaber@trash.net \
--cc=denys@visp.net.lb \
--cc=netdev@vger.kernel.org \
--cc=shemminger@linux-foundation.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.