[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20101229160607.GH14221@pengutronix.de>
Date: Wed, 29 Dec 2010 17:06:07 +0100
From: Uwe Kleine-König
<u.kleine-koenig@...gutronix.de>
To: netdev@...r.kernel.org
Subject: sysctls below net.ipv[46].conf.all not working as expected
Hello,
I did the following:
cassiopeia:~# sysctl net.ipv6.conf.all.use_tempaddr
net.ipv6.conf.all.use_tempaddr = 0
cassiopeia:~# sysctl net.ipv6.conf.eth0.use_tempaddr
net.ipv6.conf.eth0.use_tempaddr = 0
cassiopeia:~# sysctl -w net.ipv6.conf.all.use_tempaddr=1
net.ipv6.conf.all.use_tempaddr = 1
cassiopeia:~# sysctl net.ipv6.conf.all.use_tempaddr
net.ipv6.conf.all.use_tempaddr = 1
cassiopeia:~# sysctl net.ipv6.conf.eth0.use_tempaddr
net.ipv6.conf.eth0.use_tempaddr = 0
Here I would have expected that eth0's use_tempaddr is 1, too. The
problem is not that this entry isn't writeable:
cassiopeia:~# sysctl -w net.ipv6.conf.eth0.use_tempaddr=1
net.ipv6.conf.eth0.use_tempaddr = 1
cassiopeia:~# sysctl net.ipv6.conf.eth0.use_tempaddr
net.ipv6.conf.eth0.use_tempaddr = 1
I got the same results when using net.ipv4.conf.all.rp_filter (and
net.ipv4.conf.eth0.rp_filter resp.)
Is this a bug or just my failure to see how conf/all works?
Best regards
Uwe
--
Pengutronix e.K. | Uwe Kleine-König |
Industrial Linux Solutions | http://www.pengutronix.de/ |
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists