Unable to enable IPv6 Privacy Extensions on eth0

[jbeezo]

This is on a fresh install of 13.04. Network Manager keeps defaulting net.ipv6.conf.all.use_tempaddr back to 0. I'm fairly confident this problem did not exist in 12.10, but feel free to squash this ticket if it is indeed a duplicate of #990011.
Confirmed net.ipv6.conf.all.use_tempaddr is also set to 0 on my laptop running 13.04. Luckily I use eth1 (wifi in this case) which seems unaffected.

$ ls /proc/sys/net/ipv6/conf/
all default eth0 lo

$ cat /proc/sys/net/ipv6/conf/*/use_tempaddr
2
2
0
2

$ sudo sysctl net.ipv6.conf.all.use_tempaddr=0
net.ipv6.conf.all.use_tempaddr = 0

$ cat /proc/sys/net/ipv6/conf/*/use_tempaddr
0
0
0
0

$ sudo sysctl net.ipv6.conf.all.use_tempaddr=2
net.ipv6.conf.all.use_tempaddr = 2

$ cat /proc/sys/net/ipv6/conf/*/use_tempaddr
2
2
0
2

$ sudo sysctl net.ipv6.conf.eth0.use_tempaddr=2
net.ipv6.conf.eth0.use_tempaddr = 2

$ cat /proc/sys/net/ipv6/conf/eth0/use_tempaddr
0

ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: network-manager 0.9.8.0-0ubuntu6
ProcVersionSignature: Ubuntu 3.8.0-19.30-generic 3.8.8
Uname: Linux 3.8.0-19-generic x86_64
ApportVersion: 2.9.2-0ubuntu8
Architecture: amd64
CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found.
Date: Sat May 4 12:25:29 2013
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
InstallationDate: Installed on 2013-04-27 (7 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
IpRoute:
 default via 192.168.1.1 dev eth0 proto static
 169.254.0.0/16 dev eth0 scope link metric 1000
 192.168.1.0/24 dev eth0 proto kernel scope link src 192.168.1.213 metric 1
IwConfig:
 eth0 no wireless extensions.

 lo no wireless extensions.
MarkForUpload: True
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=true
 WimaxEnabled=true
RfKill:

SourcePackage: network-manager
UpgradeStatus: No upgrade log present (probably fresh install)
nmcli-con:
 NAME UUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH
 Wired connection 1 ddad2c33-3c6c-44c6-aa1a-51a13560b698 802-3-ethernet 1367695468 Sat 04 May 2013 12:24:28 PM PDT yes no /org/freedesktop/NetworkManager/Settings/0
nmcli-dev:
 DEVICE TYPE STATE DBUS-PATH
 eth0 802-3-ethernet connected /org/freedesktop/NetworkManager/Devices/0
nmcli-nm:
 RUNNING VERSION STATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN
 running 0.9.8.0 connected enabled enabled enabled enabled disabled

[jbeezo (jbeezo)]

Ah ha!
Initially I was using DHCP and while troubleshooting I noticed there were no files in /etc/NetworkManager/system-connections/
I created an arbitrary file called auto-eth0 based on http://fedoraproject.org/wiki/Tools/NetworkManager/IPv6 to no avail.

After setting a static IPv4 address using the GUI (System -> Network -> Options), I noticed a file had been created: "/etc/NetworkManager/system-connections/Wired connection 1"

Seems there is a problem invoking the creation of this file. A little finagling is required.

[jbeezo (jbeezo)]

Confirmed the bug on a fresh VM install.
New users using DHCP with no need to touch the interface settings will have an ever changing network UUID (on each network restart or reboot), and IPv6 hosts using stateless autoconfiguration will be stuck with a Modified EUI-64 address.

[Launchpad Janitor (janitor)]

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

[jbeezo (jbeezo)]

Still seeing this bug in the latest nightly with NetworkManager version 0.9.8.0.
Steps to reproduce:
1) Boot from LiveCD and Install Ubuntu
2) $ ls /etc/NetworkManager/system-connections/ #notice there are no files
3) $ nmcli c #record output
4) Reboot
5) Repeat steps 2 and 3 #still no files in the system-connections directory and now the UUID for the interface has changed
6) Click Network icon in the top-right menu bar, then "Edit Connections".
7) Select "Wired connection 1" and then click Edit.
8) Click Save then Close
9) Repeat steps 2 and 3 #notice that a config file has now been generated for "Wired connection 1"
10) Reboot
11) Repeat steps 2 and 3 #notice that the UUID is now fixed as per the auto-generated config file

[jbeezo (jbeezo)]

Still seeing this bug (ie. no automatic file creation in /etc/NetworkManager/system-connections/) in 13.10 however it has morphed slightly. After performing a fresh install, the system creates an IPv6 address consisting of the network prefix followed by an arbitrary number (well...I'm sure there's an algorithm/mechanism for generating it) for the last octet (eg. 2001:0DB8:DEAD:BEEF::123/128) and proceeds to prefer this address instead of the Modified EUI-64 address.

After following steps 6-9 above, NetworkManager starts generating and preferring privacy addresses even though the /128 still lingers.

This is all likely due to the revision bump to 0.9.8.0-0ubuntu22.

It's also worth noting that my router runs a recent trunk build of OpenWrt utilizing 6relayd.

[Renne (renne)]

I can confirm that Ubuntu 13.10 Desktop x86_64 changes the 9th octet only! Fresh install two weeks ago.