On Thu, Jan 17, 2019 at 4:25 PM Nicolas Dichtel <nicolas.dich...@6wind.com> wrote: > > Le 16/01/2019 à 09:53, xiangxia.m....@gmail.com a écrit : > > From: Tonghao Zhang <xiangxia.m....@gmail.com> > > > > The devconf setting on the init_net will affect other > > namespace when them created. For example: > > > > $ cat /proc/sys/net/ipv4/conf/all/rp_filter > > 0 > > $ echo 2 > /proc/sys/net/ipv4/conf/all/rp_filter > > $ cat /proc/sys/net/ipv4/conf/all/rp_filter > > 2 > > > > $ ip netns add ns100 > > $ ip netns exec ns100 bash > > $ cat /proc/sys/net/ipv4/conf/all/rp_filter > > 2 > > > > The value of rp_filter in the ns100, should be 0 as > > default, but it is 2 same as _init_net_. > This problem has already been discussed in the past. We cannot change anymore > the current behavior, some users are relying on it. Sorry, I don't know that some users rely on it and I send that patch again. In our case,
there are many containers, on host, where running the different type containers and applications. We don't know what network configuration user will set. The new containers don't inherit our host configuration. * host _init_net_ may be used as a complex network. (the rp_filter, arp_ignore and arp_announce may be used.) but containers use them as default. Host network configuration should not affect containers. * containers and host network configuration are complete isolation. so, we should support configuration for user, inherit _init_net_ value or not ? > > Regards, > Nicolas
