use_tempaddr always at 0 after a reboot

Bug #799322 reported by fabien29200
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
network-manager (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

I am trying IPv6 and I want to activate the privacy address mechanism.

I have read everywhere to add "net.ipv6.conf.eth1.use_tempaddr=2" to /etc/sysctl.conf.

What I did. I tried a "sysctl -p" followed by "ifconfig eth1 down" and "ifconfig eth1 up".
This worked like a charm.

But after a reboot, the value of /proc/sys/net/ipv6/conf/eth1/use_tempaddr is always 0.

I tried to add those lines :

net.ipv6.conf.all.use_tempaddr=2
net.ipv6.conf.default.use_tempaddr=2

to /etc/sysctl.conf, but nothing to do, after a reboot, the value of /proc/sys/net/ipv6/conf/eth1/use_tempaddr is always 0.

So I could write a script to make "sysctl -p; ifconfig eth1 down; ifconfig eth1 up", but I think there is a bug somewhere no ?

ProblemType: Bug
DistroRelease: Ubuntu 11.04
Package: network-manager 0.8.4~git.20110319t175609.d14809b-0ubuntu3
ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
Uname: Linux 2.6.38-8-generic x86_64
NonfreeKernelModules: nvidia
Architecture: amd64
CRDA: Error: [Errno 2] Aucun fichier ou dossier de ce type
Date: Sun Jun 19 09:33:32 2011
EcryptfsInUse: Yes
Gconf:

IfupdownConfig:
 auto lo
 iface lo inet loopback
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007.1)
IpRoute:
 192.168.1.0/24 dev eth1 proto kernel scope link src 192.168.1.1 metric 1
 169.254.0.0/16 dev eth1 scope link metric 1000
 default via 192.168.1.254 dev eth1 proto static
IwConfig:
 lo no wireless extensions.

 eth1 no wireless extensions.

 vboxnet0 no wireless extensions.
Keyfiles: Error: [Errno 2] Aucun fichier ou dossier de ce type
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=true
ProcEnviron:
 LANGUAGE=fr_FR:en
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
RfKill:

SourcePackage: network-manager
UpgradeStatus: Upgraded to natty on 2011-05-02 (47 days ago)

Revision history for this message
fabien29200 (fabien29200) wrote :
Revision history for this message
fabien29200 (fabien29200) wrote :

After watching logs, my network is first detected as eth0.

Maybe udev rename it "eth1" later.

If I had "net.ipv6.conf.eth0.use_tempaddr=2", it works fine but it's a little tricky.

affects: ubuntu → network-manager (Ubuntu)
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in network-manager (Ubuntu):
status: New → Confirmed
Revision history for this message
Mathieu Trudel-Lapierre (cyphermox) wrote :

Fixed in Precise.

Changed in network-manager (Ubuntu):
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.