From: "Linus Lüssing" <linus.luessing@c0d3.blue>
To: Jan Engelhardt <jengelh@inai.de>
Cc: netfilter-devel@vger.kernel.org,
Matthias Schiffer <mschiffer@universe-factory.net>
Subject: Re: Matching MLD with ip6tables
Date: Sat, 2 May 2015 10:58:13 +0200 [thread overview]
Message-ID: <20150502085812.GA3156@odroid> (raw)
In-Reply-To: <alpine.LSU.2.20.1505010828090.30665@nerf40.vanv.qr>
On Fri, May 01, 2015 at 08:33:03AM +0200, Jan Engelhardt wrote:
>
> On Friday 2015-05-01 04:56, Linus Lüssing wrote:
> >
> >According to RFC4890 ("Recommendations for Filtering ICMPv6
> >Messages in Firewalls"), page 35, a rule like this should match
> >MLD packets:
> >
> >$ ip6tables -A icmpv6-filter -p icmpv6 --icmpv6-type {130,131,132,143} ...
> >
> >However, this does not seem to work for me. My guess is that it
> >does not match because --protocol is not 'icmpv6' but actually
> >the hop-by-hop-option first.
> >Also, is there a way to somehow match IPv6 protocols with IPv6
> >options in between?
>
> -p matches the first non-extension header. For the
> exthdrs, there is e.g. -m hbh.
You're right, I had made a wrong assumption about ip6tables... It
wasn't ip6tables incapabilities but a bug in OpenWRT which set a
default ICMPv6 code of 255 instead of 0 when not specifying it
next to the ICMPv6 type in its config. Thanks for your help!
Awesome that ip6tables is that smart :).
Cheers, Linus
--
To unsubscribe from this list: send the line "unsubscribe netfilter-devel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2015-05-02 8:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-01 2:56 Matching MLD with ip6tables Linus Lüssing
2015-05-01 6:33 ` Jan Engelhardt
2015-05-02 8:58 ` Linus Lüssing [this message]
2015-06-16 5:45 ` Linus Lüssing
2015-06-16 7:17 ` Jan Engelhardt
2015-06-16 14:52 ` Linus Lüssing
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=20150502085812.GA3156@odroid \
--to=linus.luessing@c0d3.blue \
--cc=jengelh@inai.de \
--cc=mschiffer@universe-factory.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 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.