From: Florian Westphal <fw@strlen.de>
To: Pablo Neira Ayuso <pablo@netfilter.org>
Cc: Florian Westphal <fw@strlen.de>, Phil Sutter <phil@nwl.cc>,
netfilter-devel@vger.kernel.org
Subject: Re: Use of oifname in input chains
Date: Wed, 26 Jun 2019 12:42:54 +0200 [thread overview]
Message-ID: <20190626104254.cfhkfpagequp6kuv@breakpoint.cc> (raw)
In-Reply-To: <20190626103746.ag26jczoq7ggkh5b@salvia>
Pablo Neira Ayuso <pablo@netfilter.org> wrote:
> > new chain C
> > meta oifname bla added to C
> > jump added from output to C
> > jump added from input to C # should this fail? why?
> >
> > new chain C
> > jump added from input to C
> > meta oifname added to C # same q: why should this fail?
>
> There's tracking infrastructure for this already in place, right? It's
> just a matter to check for this from nft_meta_get_validate().
But what semantics would you add?
It seems it would 100% break existing rulesets.
new chain C
jump added from ouput to C
meta oifname added to C # allowed? jump from output exists
jump added from input to C # disallow this? Why?
..
delete jump from output # disallow?
This seems rather suicidal to me.
next prev parent reply other threads:[~2019-06-26 10:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20190625122954.GC9218@orbyte.nwl.cc>
2019-06-25 19:43 ` Use of oifname in input chains Pablo Neira Ayuso
2019-06-26 10:32 ` Florian Westphal
2019-06-26 10:37 ` Pablo Neira Ayuso
2019-06-26 10:42 ` Florian Westphal [this message]
2019-06-26 10:47 ` Pablo Neira Ayuso
2019-06-26 10:58 ` Florian Westphal
2019-06-26 12:50 ` Pablo Neira Ayuso
2019-06-26 12:56 ` Pablo Neira Ayuso
2019-06-26 12:27 ` Phil Sutter
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=20190626104254.cfhkfpagequp6kuv@breakpoint.cc \
--to=fw@strlen.de \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@netfilter.org \
--cc=phil@nwl.cc \
/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;
as well as URLs for NNTP newsgroup(s).