From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Tom <tom@foscore.com>
Cc: netfilter@vger.kernel.org
Subject: Re: Fwd: proper ICMPv6 syntax for specific daddr
Date: Thu, 8 Sep 2022 17:54:45 +0200 [thread overview]
Message-ID: <YxoQRUnq2sA+hl0x@salvia> (raw)
In-Reply-To: <59f82048-3991-2c4e-515b-4bccb24cdb98@foscore.com>
On Thu, Sep 08, 2022 at 11:43:01AM -0400, Tom wrote:
> On 2022-09-08 11:13, Pablo Neira Ayuso wrote:
> > you removed the limit line in the set declaration ?
>
> Yes, after I failed to get the right syntax to combine it with the ICMP type.
>
> > If you would like to throttle icmpv6 echo-request, the::
> >
> > table ip6 filter {
> > set ping6 {
> > typeof ip6 daddr . icmpv6 type
> > limit rate 5/second
> > elements = { aaaa:43:a:83::2 . echo-request,
> > aaaa:43:a:83::3 . echo-request,
> > aaaa:43:a:83::4 . echo-request }
> > }
> > chain input {
> > type filter hook input priority filter; policy drop;
> > ip6 daddr . icmpv6 type @ping6 accept
> > }
> > }
>
> Thanks. I wouldn't have found that syntax in a quintillion years.
It was the same as the example I posted, I just replaced 'meta l4proto' by
'icmpv6 type' ;-)
> > Please, see the wiki for more examples on concatenations and sets/maps.
>
> I've gone through it. As someone who's been programming and
> configuring computers for over forty years, I can tell you that the
> wiki documentation is not good. It seems to be written by and for
> nft developers.
Documentation can always be improved, it got better over time. We have
a good number of contributors that are not developers.
prev parent reply other threads:[~2022-09-08 15:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <dea61421-4ce1-bb68-2a74-88b6f42c299e@foscore.com>
2022-09-07 15:57 ` Fwd: proper ICMPv6 syntax for specific daddr Tom
2022-09-08 8:46 ` Reindl Harald
2022-09-08 13:31 ` Tom
2022-09-08 14:23 ` Reindl Harald
2022-09-08 15:13 ` Fwd: " Pablo Neira Ayuso
2022-09-08 15:43 ` Tom
2022-09-08 15:54 ` Pablo Neira Ayuso [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=YxoQRUnq2sA+hl0x@salvia \
--to=pablo@netfilter.org \
--cc=netfilter@vger.kernel.org \
--cc=tom@foscore.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