ipvlan: Introduce l3s mode
In a typical IPvlan L3 setup where master is in default-ns and each slave is into different (slave) ns. In this setup egress packet processing for traffic originating from slave-ns will hit all NF_HOOKs in slave-ns as well as default-ns. However same is not true for ingress processing. All these NF_HOOKs are hit only in the slave-ns skipping them in the default-ns. IPvlan in L3 mode is restrictive and if admins want to deploy iptables rules in default-ns, this asymmetric data path makes it impossible to do so. This patch makes use of the l3_rcv() (added as part of l3mdev enhancements) to perform input route lookup on RX packets without changing the skb->dev and then uses nf_hook at NF_INET_LOCAL_IN to change the skb->dev just before handing over skb to L4. Signed-off-by:Mahesh Bandewar <maheshb@google.com> CC: David Ahern <dsa@cumulusnetworks.com> Reviewed-by:
David Ahern <dsa@cumulusnetworks.com> Signed-off-by:
David S. Miller <davem@davemloft.net>
Showing
- Documentation/networking/ipvlan.txt 6 additions, 1 deletionDocumentation/networking/ipvlan.txt
- drivers/net/Kconfig 1 addition, 0 deletionsdrivers/net/Kconfig
- drivers/net/ipvlan/ipvlan.h 6 additions, 0 deletionsdrivers/net/ipvlan/ipvlan.h
- drivers/net/ipvlan/ipvlan_core.c 94 additions, 0 deletionsdrivers/net/ipvlan/ipvlan_core.c
- drivers/net/ipvlan/ipvlan_main.c 80 additions, 7 deletionsdrivers/net/ipvlan/ipvlan_main.c
- include/uapi/linux/if_link.h 1 addition, 0 deletionsinclude/uapi/linux/if_link.h
Please register or sign in to comment