From: Florian Westphal <fw@strlen.de>
To: Andreas Hoefler <andreas.hoefler@hitachi-powergrids.com>
Cc: Florian Westphal <fw@strlen.de>, Daniel <tech@tootai.net>,
Reindl Harald <h.reindl@thelounge.net>,
Pablo Neira Ayuso <pablo@netfilter.org>,
"netfilter@vger.kernel.org" <netfilter@vger.kernel.org>
Subject: Re: Is it possible to change a chains default policy when rules are already present?
Date: Fri, 14 Aug 2020 15:40:00 +0200 [thread overview]
Message-ID: <20200814134000.GG1660@breakpoint.cc> (raw)
In-Reply-To: <VI1PR06MB4639D0AB412AA72F75A96A06C5400@VI1PR06MB4639.eurprd06.prod.outlook.com>
Andreas Hoefler <andreas.hoefler@hitachi-powergrids.com> wrote:
> > Daniel <tech@tootai.net> wrote:
> > > dh@peech:~$ sudo nft add chain ip6 mangle prerouting "{ type nat hook
> > > prerouting priority -350 ; policy accept ; }"
> > > Error: Could not process rule: Operation not supported add chain ip6
> > > mangle prerouting { type nat hook prerouting priority -350; policy
> > > accept; }
> >
> > Historic artifact, try a value larger than -200, e.g. -199.
> > I've sent a patch to zap this outdated check.
>
> Didn't work for me either:
> #nft add chain ip6 x y {type filter hook input priority \-100\;}
> nft: invalid option -- '1'
Different problem. Just follow Daniels example and quote everything,
i.e. nft add chain ip6 x y "{ type filter hook input priority -100; }"
next prev parent reply other threads:[~2020-08-14 13:40 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-13 12:28 Is it possible to change a chains default policy when rules are already present? Andreas Hoefler
2020-08-13 12:48 ` Reindl Harald
2020-08-13 12:50 ` Andreas Hoefler
2020-08-13 13:38 ` Duncan Roe
2020-08-14 11:07 ` Pablo Neira Ayuso
2020-08-14 11:21 ` Daniel
2020-08-14 11:36 ` Reindl Harald
2020-08-14 12:54 ` Daniel
2020-08-14 13:08 ` Florian Westphal
2020-08-14 13:21 ` Andreas Hoefler
2020-08-14 13:40 ` Florian Westphal [this message]
2020-08-14 13:44 ` Andreas Hoefler
2020-08-14 15:31 ` Daniel
2020-08-14 14:37 ` Pablo Neira Ayuso
2020-08-14 11:43 ` Andreas Hoefler
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=20200814134000.GG1660@breakpoint.cc \
--to=fw@strlen.de \
--cc=andreas.hoefler@hitachi-powergrids.com \
--cc=h.reindl@thelounge.net \
--cc=netfilter@vger.kernel.org \
--cc=pablo@netfilter.org \
--cc=tech@tootai.net \
/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