From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Florian Westphal <fw@strlen.de>
Cc: Arturo Borrero Gonzalez <arturo@netfilter.org>,
Phil Sutter <phil@nwl.cc>,
"netfilter-devel@vger.kernel.org"
<netfilter-devel@vger.kernel.org>
Subject: Re: iptables-nft-restore issue
Date: Wed, 30 Sep 2020 14:13:14 +0200 [thread overview]
Message-ID: <20200930121314.GA21983@salvia> (raw)
In-Reply-To: <20200930115922.GC20140@breakpoint.cc>
On Wed, Sep 30, 2020 at 01:59:22PM +0200, Florian Westphal wrote:
> Arturo Borrero Gonzalez <arturo@netfilter.org> wrote:
> > Hi Phil,
> >
> > (CC'ing netfilter-devel)
> >
> > I discovered my openstack neutron linuxbridge-agent malfunctioning when using
> > iptables-nft and it seems this ruleset is causing the issue:
>
> > === 8< ===
> > *raw
> > :OUTPUT - [0:0]
> > :PREROUTING - [0:0]
If I replace these two by:
:OUTPUT ACCEPT [0:0]
:PREROUTING ACCEPT [0:0]
it works. Looks like some issue with the basechain policy?
> > :neutron-linuxbri-OUTPUT - [0:0]
> > :neutron-linuxbri-PREROUTING - [0:0]
> > -I OUTPUT 1 -j neutron-linuxbri-OUTPUT
> > -I PREROUTING 1 -j neutron-linuxbri-PREROUTING
> > -I neutron-linuxbri-PREROUTING 1 -m physdev --physdev-in brq7425e328-56 -m
> > comment --comment "Set zone for f101a28-1d" -j CT --zone 4097
> > -I neutron-linuxbri-PREROUTING 2 -i brq7425e328-56 -m comment --comment "Set
> > zone for f101a28-1d" -j CT --zone 4097
> > -I neutron-linuxbri-PREROUTING 3 -m physdev --physdev-in tap7f101a28-1d -m
> > comment --comment "Set zone for f101a28-1d" -j CT --zone 4097
> >
> > COMMIT
next prev parent reply other threads:[~2020-09-30 12:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-30 9:58 iptables-nft-restore issue Arturo Borrero Gonzalez
2020-09-30 11:59 ` Florian Westphal
2020-09-30 12:13 ` Pablo Neira Ayuso [this message]
2020-09-30 12:26 ` Pablo Neira Ayuso
2020-10-02 11:30 ` Arturo Borrero Gonzalez
2020-10-02 11:42 ` Pablo Neira Ayuso
2020-09-30 14:18 ` 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=20200930121314.GA21983@salvia \
--to=pablo@netfilter.org \
--cc=arturo@netfilter.org \
--cc=fw@strlen.de \
--cc=netfilter-devel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.