Skip to contentSkip to conversation

New: Settings to /proc/sys/net/ipv[46]/conf/all are not propagated

Bugme-new Andrew Morton 2 participants 2 messages Oct 25, 2007 1 message not in the archive

Subsystems (2)
lore
Share & tools
lore

A message that is not in the archive (sent off-list or not yet received): [email protected]/

#1 lore raw
Quoted 40 lines · On Thu, 25 Oct 2007 04:44:06 -0700 (PDT) [email protected] wrote:

http://bugzilla.kernel.org/show_bug.cgi?id=9224

           Summary: Settings to /proc/sys/net/ipv[46]/conf/all are not
                    propagated
           Product: Networking
           Version: 2.5
     KernelVersion: 2.6.24-rc1
          Platform: All
        OS/Version: Linux
              Tree: Mainline
            Status: NEW
          Severity: normal
          Priority: P1
         Component: Other
        AssignedTo: [email protected]
        ReportedBy: [email protected]

Most recent kernel where this bug did not occur: 2.6.22 (not sure)
Distribution: custom
Hardware Environment: See attached files
Software Environment: See attached files.
Problem Description: Changing a setting in /proc/sys/net/ipv[46]/conf/all does not propagate the setting to the individual network interfaces, for most settings.

Steps to reproduce:

# cat /proc/sys/net/ipv6/conf/{all,default,lo,eth0}/autoconf
1
1
1
1
# echo 0 > /proc/sys/net/ipv6/conf/all/autoconf
# echo 0 > /proc/sys/net/ipv6/conf/default/autoconf
# cat /proc/sys/net/ipv6/conf/{all,default,lo,eth0}/autoconf
0
0
1
1
Quoted 7 lines

The problem occurs for other settings than "autoconf", but not for all. "forwarding" is one which does work.

Changing settings for individual interfaces still works.

The problem is not specific to ipv6.

Apparently a regression.

#2 lore raw

In article <[email protected]> (at Thu, 25 Oct 2007 09:16:52 -0700), Andrew Morton <[email protected]> says:

Quoted 3 lines
Quoted 1 line

Most recent kernel where this bug did not occur: 2.6.22 (not sure)

Apparently a regression.

I would say it is a bug, but it is not a regression. I mean, I believe this "bug" lives since 2.2.

--yoshfuji