[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <CALYGNiNJ=LCyo4v7B1BUZH-27bc22ap-RQKpPQN7m0V3kBjkPw@mail.gmail.com>
Date: Mon, 15 Feb 2016 13:49:18 +0300
From: Konstantin Khlebnikov <koct9i@...il.com>
To: Linux Kernel Network Developers <netdev@...r.kernel.org>,
Linux Containers <containers@...ts.linux-foundation.org>
Cc: Vasily Averin <vvs@...tuozzo.com>,
David Miller <davem@...emloft.net>,
"Eric W. Biederman" <ebiederm@...ssion.com>,
Pavel Emelyanov <xemul@...tuozzo.com>
Subject: IPv4/IPv6 sysctl defaults in new namespace
IPv6 initialized with default. That's ok.
IPv4 makes a copy from init_net. Looks like a bug, here
v2.6.24-2577-g752d14dc6aa9
root@...g:~# sysctl net.ipv4.conf.all.forwarding=0
net.ipv6.conf.all.forwarding=0
net.ipv4.conf.all.forwarding = 0
net.ipv6.conf.all.forwarding = 0
root@...g:~# unshare -n sysctl net.ipv4.conf.all.forwarding
net.ipv6.conf.all.forwarding
net.ipv4.conf.all.forwarding = 0
net.ipv6.conf.all.forwarding = 0
root@...g:~# sysctl net.ipv4.conf.all.forwarding=1
net.ipv6.conf.all.forwarding=1
net.ipv4.conf.all.forwarding = 1
net.ipv6.conf.all.forwarding = 1
root@...g:~# unshare -n sysctl net.ipv4.conf.all.forwarding
net.ipv6.conf.all.forwarding
net.ipv4.conf.all.forwarding = 1
net.ipv6.conf.all.forwarding = 0
This is nasty. Could we fix this or this bug set in stone?
Powered by blists - more mailing lists