From: Thomas Graf <tgraf@suug.ch>
To: Denys Fedoryschenko <denys@visp.net.lb>
Cc: netdev@vger.kernel.org, Stephen Hemminger <shemminger@vyatta.com>
Subject: Re: iproute2, meta, flex parser bug?
Date: Fri, 30 Jan 2009 14:20:05 +0100 [thread overview]
Message-ID: <20090130132005.GK20815@postel.suug.ch> (raw)
In-Reply-To: <200901291304.24257.denys@visp.net.lb>
* Denys Fedoryschenko <denys@visp.net.lb> 2009-01-29 13:04
> I'm trying to make meta work, without success. Seems parser done in flex
> failing. My knowledge is not enough to fix or understand how flex is working
> Here is what i got:
>
> home iproute2 # home iproute2 # tc/tc filter add dev eth0 protocol ip pref 11
> basic match meta\(rt_iif eq \"eth0\"\)
Try: tc filter ... basic match 'meta(rt_iif eq <NUM>)' classid XX:YY
prev parent reply other threads:[~2009-01-30 13:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-29 11:04 iproute2, meta, flex parser bug? Denys Fedoryschenko
2009-01-30 13:20 ` Thomas Graf [this message]
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=20090130132005.GK20815@postel.suug.ch \
--to=tgraf@suug.ch \
--cc=denys@visp.net.lb \
--cc=netdev@vger.kernel.org \
--cc=shemminger@vyatta.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).