From: Florian Westphal <fw@strlen.de>
To: wenxu <wenxu@ucloud.cn>
Cc: Florian Westphal <fw@strlen.de>,
pablo@netfilter.org, netfilter-devel@vger.kernel.org,
netdev@vger.kernel.org
Subject: Re: [PATCH nf-next 1/3] netfilter: nf_nat_proto: add nf_nat_bridge_ops support
Date: Tue, 9 Jul 2019 12:42:06 +0200 [thread overview]
Message-ID: <20190709104206.gy6l52rx2dat3743@breakpoint.cc> (raw)
In-Reply-To: <0a4cf910-6c87-34b6-3018-3e25f6fecdce@ucloud.cn>
wenxu <wenxu@ucloud.cn> wrote:
> > For NAT on bridge, it should be possible already to push such packets
> > up the stack by
> >
> > bridge input meta iif eth0 ip saddr 192.168.0.0/16 \
> > meta pkttype set unicast ether daddr set 00:11:22:33:44:55
>
> yes, packet can be push up to IP stack to handle the nat through bridge device.
>
> In my case dnat 2.2.1.7 to 10.0.0.7, It assume the mac address of the two address
> is the same known by outer.
I think that in general they will have different MAC addresses, so plain
replacement of ip addresses won't work.
> But in This case modify the packet dmac to bridge device, the packet push up through bridge device
> Then do nat and route send back to bridge device.
Are you saying that you can use the send-to-ip-layer approach?
We might need/want a more convenient way to do this.
There are two ways that I can see:
1. a redirect support for nftables bridge family.
The redirect expression would be same as "ether daddr set
<bridge_mac>", but there is no need to know the bridge mac address.
2. Support ebtables -t broute in nftables.
The route rework for ebtables has been completed already, so
this needs a new expression. Packet that is brouted behaves
as if the bridge port was not part of the bridge.
next prev parent reply other threads:[~2019-07-09 10:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-08 8:29 [PATCH nf-next 1/3] netfilter: nf_nat_proto: add nf_nat_bridge_ops support wenxu
2019-07-08 8:29 ` [PATCH nf-next 2/3] netfilter: nft_chain_nat: add nft_chain_nat_bridge support wenxu
2019-07-08 8:29 ` [PATCH nf-next 3/3] netfilter: nft_nat: add nft_bridge_nat_type support wenxu
2019-07-08 14:17 ` [PATCH nf-next 1/3] netfilter: nf_nat_proto: add nf_nat_bridge_ops support Florian Westphal
2019-07-09 2:56 ` wenxu
2019-07-09 10:42 ` Florian Westphal [this message]
2019-07-09 13:38 ` wenxu
2019-07-09 7:04 ` kbuild test robot
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=20190709104206.gy6l52rx2dat3743@breakpoint.cc \
--to=fw@strlen.de \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@netfilter.org \
--cc=wenxu@ucloud.cn \
/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).