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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/994931
Title:
Altering use_tempaddr drops all IPv6 addresses
To
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-
trusty' to 'verification-done-trusty'.
If verification is not done by 5 working days from
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
** 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 Ubuntu
Bugs, which is subscribed to Ubuntu.
Thanks, Kamal!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/994931
Title:
Altering use_tempaddr drops all IPv6 addresses
To manage notifications about this bug go to:
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/994931
Title:
Altering use_tempaddr drops all IPv6 addresses
To manage notifications about this bug go to:
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/994931
Title:
Altering use_tempaddr drops all IPv6 addresses
To manage
Any chance this could be fixed in Trusty?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/994931
Title:
Altering use_tempaddr drops all IPv6 addresses
To manage notifications about this bug go to:
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 Ubuntu
Bugs, 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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/994931
Title:
Altering use_tempaddr
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
** 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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/994931
Title:
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 Ubuntu
Bugs, which is subscribed
** 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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/994931
Title:
Altering use_tempaddr drops all IPv6
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 Ubuntu
Bugs, which
** 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)
** Changed in: linux
Status: Confirmed = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/994931
Title:
Altering use_tempaddr drops all IPv6 addresses
To manage notifications about
** Changed in: linux (Ubuntu)
Status: Confirmed = Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/994931
Title:
Altering use_tempaddr drops all IPv6 addresses
To manage notifications
I've been in touch with Mathieu Trudel-Lapierre, the original author of
the Ubuntu patch I linked above, who tells me that his patch was
rejected upstream as Dave Miller does not want these semantics for 'all'
sysctls (and apparently the documentation, rather than the
implementation, is wrong):
Kernel packages with my patch applied are available in this PPA:
https://launchpad.net/~malcscott/+archive/lp994931
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/994931
Title:
Altering use_tempaddr
@Malcolm
I'll build a test kernel with the commit mentioned in comment #2
reverted. I'll post a link to the test kernel shortly.
** Changed in: linux (Ubuntu)
Importance: Undecided = Medium
** Tags added: kernel-da-key
--
You received this bug notification because you are a member of
I built a test kernel with commit
4bbefb4b1186b13d0d6100bd71d348a1efba017d reverted. The test kernel is
located at:
http://people.canonical.com/~jsalisbury/lp994931
Can you test that kernel and report back if it resolves this bug?
--
You received this bug notification because you are a member
Alternatively: here's my attempt at fixing the IPv6 Privacy
implementation. It could do with code review as I'm not absolutely sure
I've got the locking right (although I think I have!).
** Patch added: fixed IPv6 Privacy implementation
jsalisbury: problem is, simply reverting that commit leaves us with IPv6
Privacy not working at all, and it's on by default now. (There is at
least one upstream bug: e.g.
https://bugzilla.kernel.org/show_bug.cgi?id=42855)
I should add that I've tested my patch for a few days and it seems to
work
@Malcolm
Just curious if you sent your patch upstream as of yet? If you have,
what sort of feedback has it received, is it getting applied to a
subsystem maintainer's tree, etc?
People affected by this bug are probably wondering why the kernel team
doesn't just apply the patch and fix it. The
@jsalisbury
I would like to submit this upstream, although my patch is just fixing
the previous Ubuntu-specific commit I linked above. Do you know whether
that has already been sent upstream?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Tags added: patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/994931
Title:
Altering use_tempaddr drops all IPv6 addresses
To manage notifications about this bug go to:
@Malcolm
I'm not sure if this has been addressed upstream as of yet. I can do
some investigation.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/994931
Title:
Altering use_tempaddr drops all IPv6
** Changed in: linux
Status: Unknown = Confirmed
** Changed in: linux
Importance: Unknown = Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/994931
Title:
Altering use_tempaddr drops
apport information
** Tags added: apport-collected
** Description changed:
$ uname -a
Linux expvr-alnilam 3.2.0-24-generic-pae #37-Ubuntu SMP Wed Apr 25 10:47:59
UTC 2012 i686 i686 i386 GNU/Linux
$ sysctl net.ipv6.conf.eth2.use_tempaddr
net.ipv6.conf.eth2.use_tempaddr = 2
# (as
The cuplrit is likely to be lines 4355..4359 of net/ipv6/addrconf.c,
try to bring down and back up the interface to get new temporary
addresses created -- this has unwanted side-effects. This seems to be
Ubuntu-specific code introduced in http://kernel.ubuntu.com/git?p=ubuntu
/ubuntu-
41 matches
Mail list logo
