IPv6 temporary addresses accumulate over time

[Nils Ohlmeier]

On my office desktop machine I observe that it accumulates temporary IPv6 addresses over time, even though all except one are marked as deprecated already.

E.g. right now my IP list looks like this:
2: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qlen 1000
    inet6 2620:101:80fc:224:ad8a:b15b:f83e:99e9/64 scope global temporary dynamic
       valid_lft 594471sec preferred_lft 75471sec
    inet6 2620:101:80fc:224:7484:af8e:1051:52b9/64 scope global temporary deprecated dynamic
       valid_lft 508673sec preferred_lft 0sec
    inet6 2620:101:80fc:224:3855:ba9f:c4ab:5784/64 scope global temporary deprecated dynamic
       valid_lft 422875sec preferred_lft 0sec
    inet6 2620:101:80fc:224:ac16:b27:9fa4:4f5d/64 scope global temporary deprecated dynamic
       valid_lft 337078sec preferred_lft 0sec
    inet6 2620:101:80fc:224:f0c6:8f9f:74b8:99ca/64 scope global temporary deprecated dynamic
       valid_lft 251280sec preferred_lft 0sec
    inet6 2620:101:80fc:224:e070:5f9b:9783:bd0d/64 scope global temporary deprecated dynamic
       valid_lft 165483sec preferred_lft 0sec
    inet6 2620:101:80fc:224:f46a:182b:e2c8:d026/64 scope global temporary deprecated dynamic
       valid_lft 79685sec preferred_lft 0sec
    inet6 2620:101:80fc:224:baca:3aff:fea3:1b50/64 scope global mngtmpaddr noprefixroute dynamic
       valid_lft 2591996sec preferred_lft 604796sec
    inet6 fe80::baca:3aff:fea3:1b50/64 scope link
       valid_lft forever preferred_lft forever

Once I reboot the interface has only the one IP addressed based on MAC address plus one temporary address.

I verified manually via 'netstat -anp' that no active network connections or listening sockets remain on the interfaces which are marked as deprecated.

I think the deprecated addresses should be removed once no socket is any longer using the address.

ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: network-manager 1.0.4-0ubuntu5.2
ProcVersionSignature: Ubuntu 4.2.0-25.30-generic 4.2.6
Uname: Linux 4.2.0-25-generic x86_64
ApportVersion: 2.19.1-0ubuntu5
Architecture: amd64
CurrentDesktop: Unity
Date: Fri Feb 5 14:33:40 2016
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
InstallationDate: Installed on 2016-01-20 (16 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
IpRoute:
 default via 10.252.24.1 dev eno1 proto static metric 100
 10.252.24.0/21 dev eno1 proto kernel scope link src 10.252.25.160 metric 100
 10.252.75.120 via 10.252.24.1 dev eno1 proto dhcp metric 100
IwConfig:
 eno1 no wireless extensions.

 lo no wireless extensions.
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 AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH
 Wired connection 1 9950bc89-c72d-4964-9a18-e3187649321e 802-3-ethernet 1454711368 Fri 05 Feb 2016 02:29:28 PM PST yes 0 no /org/freedesktop/NetworkManager/Settings/0 yes eno1 activated /org/freedesktop/NetworkManager/ActiveConnection/1
nmcli-dev:
 DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH
 eno1 ethernet connected /org/freedesktop/NetworkManager/Devices/0 Wired connection 1 9950bc89-c72d-4964-9a18-e3187649321e /org/freedesktop/NetworkManager/ActiveConnection/1
 lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/1 -- -- --
nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'.

[Sebastien Bacher (seb128)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance.

[Aron Xu (happyaron)]

This is really a feature but not a bug, it's called IPv6 privacy extension.