Mahesh Bandewar 4fbae7d83c 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>		2016-09-19 01:25:22 -04:00
..
ipvlan_core.c	ipvlan: Introduce l3s mode	2016-09-19 01:25:22 -04:00
ipvlan_main.c	ipvlan: Introduce l3s mode	2016-09-19 01:25:22 -04:00
ipvlan.h	ipvlan: Introduce l3s mode	2016-09-19 01:25:22 -04:00
Makefile