wenxu@xxxxxxxxx <wenxu@xxxxxxxxx> wrote:
> From: wenxu <wenxu@xxxxxxxxx>
>
> Add nf_nat_bridge_ops to do nat in the bridge family
Whats the use case for this?
The reason I'm asking is that a bridge doesn't know about IP,
Bridge netfilter (the call-iptables thing) has a lot of glue code
to detect dnat rewrites and updates target mac address, including
support for redirect (suddently packet has to be pushed up the stack)
or changes in the oif to non-bridge ports (it even checks forward sysctl
state ..) and so on.
Thats something that I don't want to support in nftables.
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
then normal ip processing handles this and nat should "just work".
If above doesn't work for you I'd like to understand why.
