On Mon, Feb 29, 2016 at 2:08 PM, Mahesh Bandewar <mah...@bandewar.net> wrote: > From: Mahesh Bandewar <mahe...@google.com> > > netif_receive_skb_core() dispatcher uses skb->dev device to send it > to the packet-handlers (e.g. ip_rcv, ipv6_rcv etc). These packet > handlers intern use the device passed to determine the net-ns to > further process these packets. Now with the nomination logic, the > dispatcher will call netif_get_l3_dev() helper to select the device > to be used for this processing. Since l3_dev is initialized to self, > normal packet processing should not change. >
So, if I understand your patches correctly, _logically_ the skb is still passed into the slave's netns via dev_forward_skb() but now goes over the iptable rules from the default netns by only changing the netns parameter to these hooks? That is ugly... Logically, you should still need to continue to pass the skb upper to the stack in default netns until ip_local_deliver_finish(). So, how about adding an iptable hook in ipvlan so that skb will continue traverse in the original stack and then moved into slave's netns? This might be harder since logically we need an L3 entrance to the stack. Thoughts?
