From: Duncan Roe <duncan_roe@optusnet.com.au>
To: netfilter@vger.kernel.org
Subject: Re: nftables: How to filter only ipv6 SSH traffic in an inet table?
Date: Sun, 18 Feb 2018 19:52:52 +1100 [thread overview]
Message-ID: <20180218085252.GA5058@dimstar.local.net> (raw)
In-Reply-To: <20180218040051.GA2428@dimstar.local.net>
On Sun, Feb 18, 2018 at 03:00:51PM +1100, Duncan Roe wrote:
> Hi Merlin,
>
> On Thu, Feb 08, 2018 at 04:14:15AM +0100, Merlin Büge wrote:
> > On Wed, 7 Feb 2018 20:26:32 +0100
> > Pablo Neira Ayuso <pablo@netfilter.org> wrote:
...
>
> > #!/usr/sbin/nft -f
> > flush ruleset
> >
> > # (existing table omitted)
> >
> > table inet filter \
> > {
> > chain input \
> > {
> > type filter hook input priority 100; policy drop;
> >
> > # Only for wlan0
> > iif ne "wlan0" accept
> >
> > ip6 nexthdr tcp tcp dport ssh counter drop;
> > meta nfproto ipv6 tcp dport ssh counter accept
> > counter log prefix "nft6: " level debug
> > }
> > }
> > list ruleset
>
> *list ruleset* above produced the following:
>
> > table inet filter {
> > chain input {
> > type filter hook input priority 100; policy drop;
> > iif != "wlan0" accept
> > meta nfproto ipv6 ip6 nexthdr tcp tcp dport ssh counter packets 0 bytes 0 accept
> > meta nfproto ipv6 meta l4proto tcp tcp dport ssh counter packets 0 bytes 0 accept
> > counter packets 0 bytes 0 log prefix "nft6: " level debug
> > }
> > }
>
> while stand-alone *nft list ruleset* shows:
>
> > table inet filter {
> > chain input {
> > type filter hook input priority 100; policy drop;
> > iif != "wlan0" accept
> > tcp dport ssh counter packets 0 bytes 0 accept
> > tcp dport ssh counter packets 0 bytes 0 accept
> > counter packets 0 bytes 0 log prefix "nft6: " level debug
> > }
> > }
>
I just re-tried this with the latest git snapshot (latest change 2018-02-15),
and the output from stand-alone *nft list ruleset* has changed to:
> table inet filter {
> chain input {
> type filter hook input priority 100; policy drop;
> iif != "wlan0" accept
> ip6 nexthdr tcp tcp dport ssh counter packets 0 bytes 0 accept
> meta nfproto ipv6 tcp dport ssh counter packets 0 bytes 0 accept
> meta l4proto ipv6-icmp counter packets 1 bytes 72 accept
> counter packets 1 bytes 84 log prefix "nft6: " level debug
> }
> }
i.e. exactly as per the original script (whitespace and counter values excepted)
Cheers ... Duncan.
prev parent reply other threads:[~2018-02-18 8:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-06 16:28 nftables: How to filter only ipv6 SSH traffic in an inet table? Merlin Büge
2018-02-07 0:32 ` Duncan Roe
2018-02-07 19:26 ` Pablo Neira Ayuso
2018-02-08 3:14 ` Merlin Büge
2018-02-18 4:00 ` Duncan Roe
2018-02-18 4:10 ` Duncan Roe
2018-02-18 8:52 ` Duncan Roe [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=20180218085252.GA5058@dimstar.local.net \
--to=duncan_roe@optusnet.com.au \
--cc=netfilter@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