This bug was fixed in the package linux - 3.2.0-111.153
---
linux (3.2.0-111.153) precise; urgency=low
[ Kamal Mostafa ]
* Release Tracking Bug
- LP: #1626151
* Altering use_tempaddr drops all IPv6 addresses (LP: #994931)
- Revert "UBUNTU: SAUCE: ipv6: make the
This bug was fixed in the package linux - 3.2.0-111.153
---
linux (3.2.0-111.153) precise; urgency=low
[ Kamal Mostafa ]
* Release Tracking Bug
- LP: #1626151
* Altering use_tempaddr drops all IPv6 addresses (LP: #994931)
- Revert "UBUNTU: SAUCE: ipv6: make the
This bug was fixed in the package linux - 3.13.0-98.145
---
linux (3.13.0-98.145) trusty; urgency=low
* Fix GRO recursion overflow for tunneling protocols (LP: #1631287)
- tunnels: Don't apply GRO to multiple layers of encapsulation.
* CVE-2016-7039
- SAUCE: net: add
This bug was fixed in the package linux - 3.13.0-98.145
---
linux (3.13.0-98.145) trusty; urgency=low
* Fix GRO recursion overflow for tunneling protocols (LP: #1631287)
- tunnels: Don't apply GRO to multiple layers of encapsulation.
* CVE-2016-7039
- SAUCE: net: add
** Tags removed: verification-needed-precise
** Tags added: verification-done-precise
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/994931
Title:
Altering use_tempaddr drops all IPv6
Verified on trusty. Unfortunately I don't have a precise machine
anymore. After toggling use_tempaddr not all public addresses
disappeared with the new kernel while it happened with the old pre-
reboot.
** Tags removed: verification-needed-trusty
** Tags added: verification-done-trusty
--
You
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
precise' to 'verification-done-precise'.
If verification is not done by 5 working days
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
trusty' to 'verification-done-trusty'.
If verification is not done by 5 working days from
** Changed in: linux (Ubuntu Trusty)
Status: In Progress => Fix Committed
** Changed in: linux (Ubuntu Precise)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Thanks, Kamal!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/994931
Title:
Altering use_tempaddr drops all IPv6 addresses
Status in Linux:
Invalid
Status in linux package in Ubuntu:
I'm not sure how/why this issue fell by the wayside, but the tested
patch sets have (just now) been submitted for review and inclusion in
both Precise and Trusty:
https://lists.ubuntu.com/archives/kernel-team/2016-September/080007.html
--
You received this bug notification because you are a
Where did this get stuck?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/994931
Title:
Altering use_tempaddr drops all IPv6 addresses
Status in Linux:
Invalid
Status in linux package
Ping.
The test kernel seems to fix this. Could it be pushed to Trusty?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/994931
Title:
Altering use_tempaddr drops all IPv6 addresses
Any chance this could be fixed in Trusty?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/994931
Title:
Altering use_tempaddr drops all IPv6 addresses
Status in Linux:
Invalid
Status
The test kernel works (and fixes the problem) on precise, on our trusty
test server we don't have any network devices (other than lo0) with the
test kernel booted, so we can't really test the IPv6 aspect.
--
You received this bug notification because you are a member of Kernel
Packages, which is
I can't exactly test that IPv6 is fine in general with this, but it
doesn't appear to have regressed on Trusty.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/994931
Title:
Altering
Test kernels for this issue (as explained in comment #23) are now
available for Precise (3.2-based) and Trusty (3.13-based), for both
amd64 and i386 systems. To test, download *one* of these then install
with dpkg -i thatfile.deb:
I have prepared a test 3.13 kernel (for Trusty) which reverts the
Ubuntu-specific patch and adds the set of mainline patches that obviate
these issues in Utopic and newer versions. My cursory testing suggests
that it resolves both this bug (drops all IPv6 addresses) and the
problem that the
Just clarifying: This wasn't Fix Released for Utopic; it just was
never an issue in Utopic (because only Precise and Trusty carry the
Ubuntu-specific patch that triggers it).
** Changed in: linux (Ubuntu Utopic)
Status: Fix Released = Invalid
** Changed in: linux (Ubuntu Utopic)
We just had this bug take out two v6 environments (Canonical UK office
and Canonical VPN) after a procps package upgrade; it'd be wonderful if
we could get whatever is in utopic SRUed to the LTSes.
--
You received this bug notification because you are a member of Kernel
Packages, which is
** Changed in: linux (Ubuntu Precise)
Importance: Undecided = High
** Changed in: linux (Ubuntu Trusty)
Importance: Undecided = High
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Changed in: linux (Ubuntu)
Assignee: Tim Gardner (timg-tpi) = Kamal Mostafa (kamalmostafa)
** Changed in: linux (Ubuntu Precise)
Assignee: Tim Gardner (timg-tpi) = Kamal Mostafa (kamalmostafa)
** Changed in: linux (Ubuntu Trusty)
Assignee: Tim Gardner (timg-tpi) = Kamal Mostafa
verified this works as expected in utopic.
$ vals() { for i in net.ipv6.conf.all.use_tempaddr
net.ipv6.conf.default.use_tempaddr; do
[ -n $1 ] { sudo sysctl $i=$1 || return; } || sysctl $i;
done; }
$ vals 0
net.ipv6.conf.all.use_tempaddr = 0
The patch for this is currently stalled waiting on feedback on the
locking model in the patch.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/994931
Title:
Altering use_tempaddr drops
Just ran into this here. I set use_tempaddr=0 in my sysctl.conf, and
was very confused why my IPv6 wasn't coming up on boot. Can confirm
this is why.
This really needs to be fixed as it breaks IPv6 on boot.
--
You received this bug notification because you are a member of Kernel
Packages,
** Also affects: linux (Ubuntu Trusty)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Precise)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Utopic)
Importance: Medium
Status: Triaged
** Changed in: linux (Ubuntu Precise)
26 matches
Mail list logo
