From: Phil Sutter <phil@nwl.cc>
To: Pablo Neira Ayuso <pablo@netfilter.org>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: [nft PATCH] proto: Add some exotic ICMPv6 types
Date: Wed, 15 Mar 2017 20:50:51 +0100 [thread overview]
Message-ID: <20170315195051.GE17939@orbyte.nwl.cc> (raw)
In-Reply-To: <20170315161514.GB28159@salvia>
On Wed, Mar 15, 2017 at 05:15:14PM +0100, Pablo Neira Ayuso wrote:
> On Wed, Mar 15, 2017 at 04:55:01PM +0100, Phil Sutter wrote:
> > This adds support for matching on inverse ND messages as defined by
> > RFC3122 (not implemented in Linux) and MLDv2 as defined by RFC3810.
> >
> > Note that ICMPV6_MLD2_REPORT macro is defined in linux/icmpv6.h but
> > including that header leads to conflicts with symbols defined in
> > netinet/icmp6.h.
> >
> > In addition to the above, "mld-listener-done" is introduced as an alias
> > for "mld-listener-reduction".
> >
> > Signed-off-by: Phil Sutter <phil@nwl.cc>
> > ---
> > This should resolve netfilter BZ#926.
> > ---
> > src/proto.c | 8 ++++++++
> > 1 file changed, 8 insertions(+)
> >
> > diff --git a/src/proto.c b/src/proto.c
> > index fb965304e59d9..6a8eed936d858 100644
> > --- a/src/proto.c
> > +++ b/src/proto.c
> > @@ -632,6 +632,10 @@ const struct proto_desc proto_ip = {
> >
> > #include <netinet/icmp6.h>
> >
> > +#define IND_NEIGHBOR_SOLICIT 141
> > +#define IND_NEIGHBOR_ADVERT 142
> > +#define ICMPV6_MLD2_REPORT 143
> > +
> > static const struct symbol_table icmp6_type_tbl = {
> > .base = BASE_DECIMAL,
> > .symbols = {
> > @@ -644,12 +648,16 @@ static const struct symbol_table icmp6_type_tbl = {
> > SYMBOL("mld-listener-query", MLD_LISTENER_QUERY),
> > SYMBOL("mld-listener-report", MLD_LISTENER_REPORT),
> > SYMBOL("mld-listener-reduction", MLD_LISTENER_REDUCTION),
> > + SYMBOL("mld-listener-done", MLD_LISTENER_REDUCTION),
>
> This one is duplicated, right?
Yes, it is the alias which was suggested in the ticket. Is this OK, or
should we rather respond with WONTFIX?
I realize this patch lacks an update to man page and a few test cases.
Should I reroll or send a follow-up?
Thanks, Phil
next prev parent reply other threads:[~2017-03-15 19:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-15 15:55 [nft PATCH] proto: Add some exotic ICMPv6 types Phil Sutter
2017-03-15 16:15 ` Pablo Neira Ayuso
2017-03-15 19:50 ` Phil Sutter [this message]
2017-03-15 21:47 ` Pablo Neira Ayuso
2017-03-16 12:43 ` [nft PATCH v2 1/2] " Phil Sutter
2017-03-16 12:43 ` [nft PATCH v2 2/2] doc: Describe ICMP(v6) expression and types Phil Sutter
2017-03-17 11:45 ` Pablo Neira Ayuso
2017-03-17 11:45 ` [nft PATCH v2 1/2] proto: Add some exotic ICMPv6 types Pablo Neira Ayuso
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=20170315195051.GE17939@orbyte.nwl.cc \
--to=phil@nwl.cc \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@netfilter.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).