From: Florian Westphal <fw@strlen.de>
To: Robert Sander <r.sander@heinlein-support.de>
Cc: netfilter@vger.kernel.org
Subject: Re: nftables iifname and currently unknown interfaces
Date: Fri, 16 Oct 2020 12:56:12 +0200 [thread overview]
Message-ID: <20201016105612.GH16895@breakpoint.cc> (raw)
In-Reply-To: <c382354e-4a18-0863-e006-0db6f9fce1f6@heinlein-support.de>
Robert Sander <r.sander@heinlein-support.de> wrote:
> Hi.
>
> with iptables it was possible to specify "-i ifacename" even when the
> interface was currently not available.
>
> nft bails out with an error:
>
> ./nft:225:1-75: Error: Could not process rule: No such file or directory
> add rule ip filter FORWARD iifname bond0.16 oifname bond0.42 accept
This error is not related to the interface names.
nft should annotate this error with ^^^^ markers with more recent
version, e.g.:
nft add rule inet filter forwad iifname bond0.16 oifname bond0.42 accept
Error: Could not process rule: No such file or directory
add rule inet filter forwad iifname bond0.16 oifname bond0.42 accept
^^^^^^
(typo in chain name).
next prev parent reply other threads:[~2020-10-16 10:56 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-16 10:37 nftables iifname and currently unknown interfaces Robert Sander
2020-10-16 10:54 ` Pablo Neira Ayuso
2020-10-16 10:56 ` Florian Westphal [this message]
2020-10-16 11:10 ` Robert Sander
2020-10-28 22:25 ` Pablo Neira Ayuso
2020-11-04 5:30 ` Trying to provision flowtable returns error Martin Gignac
2020-11-05 0:53 ` Duncan Roe
2020-11-05 15:17 ` Martin Gignac
2020-11-05 15:38 ` Florian Westphal
2020-11-05 16:20 ` Martin Gignac
2020-11-05 17:07 ` Florian Westphal
2020-11-05 18:21 ` Martin Gignac
2020-11-05 18:41 ` Martin Gignac
2020-11-05 21:01 ` Pablo Neira Ayuso
2020-11-05 21:45 ` Martin Gignac
2020-11-06 10:58 ` Pablo Neira Ayuso
2020-11-06 15:13 ` Martin Gignac
2020-11-06 15:24 ` Martin Gignac
2020-11-06 16:21 ` Pablo Neira Ayuso
2020-11-06 19:20 ` Martin Gignac
2020-11-10 15:04 ` Gordon Fisher
2020-11-06 17:18 ` 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=20201016105612.GH16895@breakpoint.cc \
--to=fw@strlen.de \
--cc=netfilter@vger.kernel.org \
--cc=r.sander@heinlein-support.de \
/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