From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Patrick McHardy <kaber@trash.net>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: [PATCH nft 1/3] parser: fix parsing of ethernet protocol types
Date: Thu, 16 Jan 2014 17:49:37 +0100 [thread overview]
Message-ID: <20140116164937.GA5179@localhost> (raw)
In-Reply-To: <20140116162816.GA4111@macbook.localnet>
On Thu, Jan 16, 2014 at 04:28:16PM +0000, Patrick McHardy wrote:
> On Wed, Jan 15, 2014 at 09:30:21PM +0100, Pablo Neira Ayuso wrote:
> > This allows us to use the protocol type keyword, eg.
> >
> > nft add rule ip filter output meta protocol ip6 counte
> > ^^^
>
> I see two problems with this patch:
>
> - the mapping to ETH_P_* is fixed. In case of f.i. meta nfproto relational
> expression it would have to map to NFPROTO_* values. So I think we should
> use symbolic expressions instead of constants and leave parsing to the
> evaluation phase-
Yes, that change needs to be done in next-3.14 to get it working with
your new inet table. I was focusing to fix this in master for the
upcoming release.
> - we're still using a mix of ip6 and ipv6. Lets also fix that, ideally
> as a patch before this one.
>
> I can take care of this if you like.
Please, go ahead, I'm looking at more pending stuff I want to provide
feedback on.
next prev parent reply other threads:[~2014-01-16 16:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-15 20:30 [PATCH nft 1/3] parser: fix parsing of ethernet protocol types Pablo Neira Ayuso
2014-01-15 20:30 ` [PATCH nft 2/3] payload: fix crash when wrong ethernet protocol type is used Pablo Neira Ayuso
2014-01-16 16:29 ` Patrick McHardy
2014-01-15 20:30 ` [PATCH nft 3/3] payload: fix inconsistency in ethertype output Pablo Neira Ayuso
2014-01-16 16:32 ` Patrick McHardy
2014-01-16 16:28 ` [PATCH nft 1/3] parser: fix parsing of ethernet protocol types Patrick McHardy
2014-01-16 16:49 ` Pablo Neira Ayuso [this message]
2014-01-16 16:51 ` Patrick McHardy
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=20140116164937.GA5179@localhost \
--to=pablo@netfilter.org \
--cc=kaber@trash.net \
--cc=netfilter-devel@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 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).