From: Florian Westphal <fw@strlen.de>
To: "Linus Lüssing" <linus.luessing@c0d3.blue>
Cc: Florian Westphal <fw@strlen.de>, netfilter@vger.kernel.org
Subject: Re: bridge-nf-call-iptables: checking bridge vs. IP context?
Date: Tue, 30 Mar 2021 19:33:18 +0200 [thread overview]
Message-ID: <20210330173318.GA17285@breakpoint.cc> (raw)
In-Reply-To: <20210329232423.GF2742@otheros>
Linus Lüssing <linus.luessing@c0d3.blue> wrote:
> Ah! Okay, so adding something like
> "-m physdev ! --physdev-is-in" to all OpenWrt firewall rules should work?
Yes.
> So from a bridge netfilter hook "--physdev-in" will always either
> point to a bridge port or the bridge interface itself?
> And "--physdev-is-in" will always be true?
--physdev-is-in is true when call-iptables infra is 1 and packet
came in via a bridge port.
> And in "native" IP netfilter hooks "--physdev-in" will never match
It won't match if packet came in via a normal (not bridged)
interface.
> and "--physdev-is-in" will always be false?
Yes.
prev parent reply other threads:[~2021-03-30 17:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-29 18:08 bridge-nf-call-iptables: checking bridge vs. IP context? Linus Lüssing
2021-03-29 19:02 ` Florian Westphal
2021-03-29 23:24 ` Linus Lüssing
2021-03-30 17:33 ` Florian Westphal [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=20210330173318.GA17285@breakpoint.cc \
--to=fw@strlen.de \
--cc=linus.luessing@c0d3.blue \
--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