netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
To: netdev@vger.kernel.org
Subject: sysctls below net.ipv[46].conf.all not working as expected
Date: Wed, 29 Dec 2010 17:06:07 +0100	[thread overview]
Message-ID: <20101229160607.GH14221@pengutronix.de> (raw)

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/  |

             reply	other threads:[~2010-12-29 16:06 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-29 16:06 Uwe Kleine-König [this message]
2010-12-30 20:20 ` sysctls below net.ipv[46].conf.all not working as expected Uwe Kleine-König
2010-12-30 20:30 ` David Miller
2010-12-30 20:43   ` Uwe Kleine-König
2011-02-22  9:34     ` Uwe Kleine-König

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20101229160607.GH14221@pengutronix.de \
    --to=u.kleine-koenig@pengutronix.de \
    --cc=netdev@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).