IPv6 Privacy Extensions do not work

Bug #1635171 reported by Marcel
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

On my Ubuntu 14.04.5 Server IPv6 Privacy Extensions do not work any more after upgrading to kernel 3.13.0-100-generic, although privacy extensions are enabled in the config:

root@Sputnik:~# cat /etc/sysctl.d/10-ipv6-privacy.conf | grep tempaddr
net.ipv6.conf.all.use_tempaddr = 2
net.ipv6.conf.default.use_tempaddr = 2

Although the privacy extensions seem to be enabled generally, they are somehow not enabled for my primary network interface eth0:

root@Sputnik:~# sysctl -a | grep tempaddr
net.ipv6.conf.all.use_tempaddr = 2
net.ipv6.conf.default.use_tempaddr = 2
net.ipv6.conf.eth0.use_tempaddr = 0
net.ipv6.conf.lo.use_tempaddr = -1
net.ipv6.conf.wlan0.use_tempaddr = 2
---
AlsaDevices:
 total 0
 crw-rw---- 1 root audio 116, 1 Okt 20 08:48 seq
 crw-rw---- 1 root audio 116, 33 Okt 20 08:48 timer
AplayDevices: Error: [Errno 2] No such file or directory
ApportVersion: 2.14.1-0ubuntu3.21
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
CRDA: Error: [Errno 2] No such file or directory
DistroRelease: Ubuntu 14.04
InstallationDate: Installed on 2015-03-21 (579 days ago)
InstallationMedia: Ubuntu-Server 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.3)
Lsusb:
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 002 Device 003: ID 8087:07dc Intel Corp.
 Bus 002 Device 002: ID 0bc2:0503 Seagate RSS LLC ST3250824A [Barracuda 7200.9]
 Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: ��������������������������������� ���������������������������������
Package: linux (not installed)
PciMultimedia:

ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-100-generic root=UUID=d4ddc9f5-eaaf-4ca1-b289-95e8ea9bb598 ro biosdevname=0 biosdevname=0
ProcVersionSignature: Ubuntu 3.13.0-100.147-generic 3.13.11-ckt39
RelatedPackageVersions:
 linux-restricted-modules-3.13.0-100-generic N/A
 linux-backports-modules-3.13.0-100-generic N/A
 linux-firmware 1.127.22
RfKill: Error: [Errno 2] No such file or directory
Tags: trusty
Uname: Linux 3.13.0-100-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm
_MarkForUpload: True
dmi.bios.date: 01/29/2015
dmi.bios.vendor: Intel Corp.
dmi.bios.version: FYBYT10H.86A.0048.2015.0129.1411
dmi.board.asset.tag: ���������������������������������
dmi.board.name: DN2820FYK
dmi.board.vendor: Intel Corporation
dmi.board.version: H24582-204
dmi.chassis.asset.tag: ���������������������������������
dmi.chassis.type: 3
dmi.chassis.vendor: ���������������������������������
dmi.chassis.version: ���������������������������������
dmi.modalias: dmi:bvnIntelCorp.:bvrFYBYT10H.86A.0048.2015.0129.1411:bd01/29/2015:svn:pn:pvr:rvnIntelCorporation:rnDN2820FYK:rvrH24582-204:cvn:ct3:cvr:
dmi.product.name: ���������������������������������
dmi.product.version: ���������������������������������
dmi.sys.vendor: ���������������������������������

Martin Pitt (pitti)
affects: systemd (Ubuntu) → linux (Ubuntu)
Revision history for this message
Brad Figg (brad-figg) wrote : Missing required logs.

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1635171

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: New → Incomplete
tags: added: trusty
Revision history for this message
Marcel (matzzzl) wrote : BootDmesg.txt

apport information

tags: added: apport-collected
description: updated
Revision history for this message
Marcel (matzzzl) wrote : CurrentDmesg.txt

apport information

Revision history for this message
Marcel (matzzzl) wrote : IwConfig.txt

apport information

Revision history for this message
Marcel (matzzzl) wrote : Lspci.txt

apport information

Revision history for this message
Marcel (matzzzl) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
Marcel (matzzzl) wrote : ProcInterrupts.txt

apport information

Revision history for this message
Marcel (matzzzl) wrote : ProcModules.txt

apport information

Revision history for this message
Marcel (matzzzl) wrote : UdevDb.txt

apport information

Revision history for this message
Marcel (matzzzl) wrote : UdevLog.txt

apport information

Revision history for this message
Marcel (matzzzl) wrote : WifiSyslog.txt

apport information

Marcel (matzzzl)
Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Does this issue go away if you boot back into the prior kernel version?

Changed in linux (Ubuntu):
importance: Undecided → Medium
tags: added: kernel-da-key
Revision history for this message
Marcel (matzzzl) wrote :

If I boot back into kernel version 3.13.0-96, the problem disappears.
With the prior kernel version 3.13.0-98 I have the same problem as with version 3.13.0-100 (but I think I just did not notice that this problem also occured with this prior version).

On my desktop machine, which runs the same Ubuntu version 14.04 but configures the network settings with the Network-Manager (instead of the setting "iface eth0 inet6 auto" in "/etc/network/interfaces"), this problem does NOT occur.

tags: added: needs-bisect
Revision history for this message
Marcel (matzzzl) wrote :

A workaround:

Add the line "net.ipv6.conf.eth0.use_tempaddr = 2" (with "eth0" being the network inferface) to "/etc/sysctl.d/10-ipv6-privacy.conf"

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.