[Desktop-packages] [Bug 1609898] Re: dhclient incorrectly assumes a /64 ipv6 prefix

2019-05-25 Thread Dan Streetman
** Changed in: network-manager (Ubuntu Trusty) Status: Triaged => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1609898 Title: dhclient incorrectly assumes

[Desktop-packages] [Bug 1609898] Re: dhclient incorrectly assumes a /64 ipv6 prefix

2016-10-12 Thread Launchpad Bug Tracker
This bug was fixed in the package network-manager - 1.2.2-0ubuntu0.16.04.3 --- network-manager (1.2.2-0ubuntu0.16.04.3) xenial; urgency=medium * debian/tests/wpa-dhclient: Don't assume that the IPv6 prefix length from the DHCP server is /64. (LP: #1609898) network-manager

[Desktop-packages] [Bug 1609898] Re: dhclient incorrectly assumes a /64 ipv6 prefix

2016-09-30 Thread LaMont Jones
After further checking, comcast is sending them, my machine is just not seeing them... Will file a separate bug. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1609898 Title:

[Desktop-packages] [Bug 1609898] Re: dhclient incorrectly assumes a /64 ipv6 prefix

2016-09-30 Thread LaMont Jones
I have confirmed that the machine is accepting router advertisements, and that comcast is not sending them. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1609898 Title:

[Desktop-packages] [Bug 1609898] Re: dhclient incorrectly assumes a /64 ipv6 prefix

2016-09-30 Thread LaMont Jones
With this fix, my IPv6 service from Comcast broke. Specifically, they hand out an IP on the /64 via dhcpv6, with the default gateway being an IP on the same /64, along with an IA /56 for the customer to use locally. Adding the default route fails because there is no route to said gateway (since

[Desktop-packages] [Bug 1609898] Re: dhclient incorrectly assumes a /64 ipv6 prefix

2016-09-28 Thread Launchpad Bug Tracker
This bug was fixed in the package isc-dhcp - 4.3.3-5ubuntu14 --- isc-dhcp (4.3.3-5ubuntu14) yakkety; urgency=medium * Add an initramfs-tools hook and ship everything we need to run dhclient in the initramfs. This is necessary for proper IPv6 netboot support. (LP: #1621507)

[Desktop-packages] [Bug 1609898] Re: dhclient incorrectly assumes a /64 ipv6 prefix

2016-09-28 Thread Launchpad Bug Tracker
This bug was fixed in the package network-manager - 1.2.4-0ubuntu1 --- network-manager (1.2.4-0ubuntu1) yakkety; urgency=medium [ Aron Xu ] * Imported Upstream version 1.2.4 * Update patches for new upstream release: -

[Desktop-packages] [Bug 1609898] Re: dhclient incorrectly assumes a /64 ipv6 prefix

2016-09-27 Thread Mathew Hodson
** Changed in: network-manager (Ubuntu Xenial) Importance: Undecided => Medium ** Changed in: network-manager (Ubuntu Trusty) Importance: Undecided => Medium -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in

[Desktop-packages] [Bug 1609898] Re: dhclient incorrectly assumes a /64 ipv6 prefix

2016-09-27 Thread Martin Pitt
http://autopkgtest.ubuntu.com/packages/n/network-manager succeeds again on xenial, thus verified. ** Tags removed: verification-done-precise verification-done-trusty verification-done-xenial verification-done-yakkety verification-needed ** Tags added: verification-done -- You received this bug

[Desktop-packages] [Bug 1609898] Re: dhclient incorrectly assumes a /64 ipv6 prefix

2016-09-27 Thread Andy Whitcroft
Hello Dan, or anyone else affected, Accepted network-manager into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/network- manager/1.2.2-0ubuntu0.16.04.3 in a few hours, and then in the -proposed repository. Please help us by testing this new

[Desktop-packages] [Bug 1609898] Re: dhclient incorrectly assumes a /64 ipv6 prefix

2016-09-27 Thread Martin Pitt
Cherry-picked into xenial branch. ** Changed in: network-manager (Ubuntu Xenial) Status: Triaged => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1609898

[Desktop-packages] [Bug 1609898] Re: dhclient incorrectly assumes a /64 ipv6 prefix

2016-09-26 Thread Launchpad Bug Tracker
This bug was fixed in the package isc-dhcp - 4.1.ESV-R4-0ubuntu5.11 --- isc-dhcp (4.1.ESV-R4-0ubuntu5.11) precise; urgency=medium * Don't assume IPv6 prefix length of 64 (LP: #1609898). Pulled from debian commit c347ab8a43587164486ce1f104eedfd638594e59. -- Dan Streetman

[Desktop-packages] [Bug 1609898] Re: dhclient incorrectly assumes a /64 ipv6 prefix

2016-09-26 Thread Launchpad Bug Tracker
This bug was fixed in the package isc-dhcp - 4.2.4-7ubuntu12.7 --- isc-dhcp (4.2.4-7ubuntu12.7) trusty; urgency=medium * Don't assume IPv6 prefix length of 64 (LP: #1609898). Pulled from debian commit c347ab8a43587164486ce1f104eedfd638594e59. -- Dan Streetman

[Desktop-packages] [Bug 1609898] Re: dhclient incorrectly assumes a /64 ipv6 prefix

2016-09-26 Thread Launchpad Bug Tracker
This bug was fixed in the package isc-dhcp - 4.3.3-5ubuntu12.3 --- isc-dhcp (4.3.3-5ubuntu12.3) xenial; urgency=medium [ Mathieu Trudel-Lapierre ] * debian/isc-dhcp-client.install: install new files for initramfs-tools to their proper locations; from debian/initramfs-tools.

[Desktop-packages] [Bug 1609898] Re: dhclient incorrectly assumes a /64 ipv6 prefix

2016-09-23 Thread Dan Streetman
Also note that dnsmasq can act as both a dhcpv6 server as well as serving router advertisements. The ISC dhcp server only does dhcpv6, it does not have support (that I know of) for serving router advertisements. If you do want your clients to use slaac addresses in addition to the dhcpv6

[Desktop-packages] [Bug 1609898] Re: dhclient incorrectly assumes a /64 ipv6 prefix

2016-09-23 Thread Dan Streetman
For anyone reading this because the isc-dhcp-client update broke their DHCPv6 network: First, I assume you're running a DHCPv6 server to provide the ipv6 addresses to your clients. If you do not have any Router Advertisement service configured on your server, the easiest thing to do is use

[Desktop-packages] [Bug 1609898] Re: dhclient incorrectly assumes a /64 ipv6 prefix

2016-09-22 Thread Martin Pitt
Adjusted the network-manager test for yakkety: https://git.launchpad.net /~network-manager/network-manager/+git/ubuntu/commit/?id=756271bf57 ** Changed in: network-manager (Ubuntu Yakkety) Importance: Undecided => Medium ** Changed in: network-manager (Ubuntu Yakkety) Status: New =>

[Desktop-packages] [Bug 1609898] Re: dhclient incorrectly assumes a /64 ipv6 prefix

2016-09-21 Thread Mathew Hodson
** Description changed: [Impact] clients who get an ipv6 address from a dhcpv6 server assume the address has a /64 prefix, but that is not necessarily true, and if the subnet is different than /64 those clients will not be able to reach other addresses in that /64 prefix because the

[Desktop-packages] [Bug 1609898] Re: dhclient incorrectly assumes a /64 ipv6 prefix

2016-09-21 Thread Dan Streetman
Unfortunately, while I initially put in the bug description that there was no regresssion potential, I've been made aware that some network configurations rely on the previous (incorrect) behavior of the dhcp client to set a prefix len of /64. Such configurations will break when the dhcp clients

[Desktop-packages] [Bug 1609898] Re: dhclient incorrectly assumes a /64 ipv6 prefix

2016-09-21 Thread Dan Streetman
@arges, yep the attached lp1609898-nm-[trusty|xenial|yakkety].debdiff patches update network-manager's test script to the new behavior. I can pull the patches out of the debdiffs, if that's easier. I did a brief search in the network-manager tests and didn't find any other place that looks like

[Desktop-packages] [Bug 1609898] Re: dhclient incorrectly assumes a /64 ipv6 prefix

2016-09-21 Thread Chris J Arges
@ddstreet, Can you propose a patch for network manager to adjust test cases to this new behavior? I'm wondering if there are other parts of network-manager that may expect /64 instead of /128 and break existing users. -- You received this bug notification because you are a member of Desktop

[Desktop-packages] [Bug 1609898] Re: dhclient incorrectly assumes a /64 ipv6 prefix

2016-09-15 Thread Dan Streetman
The attached debdiffs lp1609898-nm-[trusty|xenial|yakkety].debdiff patch network-manager's debian/tests/wpa-dhclient test to use /128 instead of /64 for its DHCPv6 address test. Note it leaves the ipv6 Router Advertisement provided addresses with /64, as that prefix length is provided to the

[Desktop-packages] [Bug 1609898] Re: dhclient incorrectly assumes a /64 ipv6 prefix

2016-09-15 Thread Dan Streetman
** Patch added: "lp1609898-nm-yakkety.debdiff" https://bugs.launchpad.net/ubuntu/precise/+source/network-manager/+bug/1609898/+attachment/4741543/+files/lp1609898-nm-yakkety.debdiff -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to

[Desktop-packages] [Bug 1609898] Re: dhclient incorrectly assumes a /64 ipv6 prefix

2016-09-15 Thread Dan Streetman
** Patch added: "lp1609898-nm-xenial.debdiff" https://bugs.launchpad.net/ubuntu/precise/+source/network-manager/+bug/1609898/+attachment/4741542/+files/lp1609898-nm-xenial.debdiff -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to

[Desktop-packages] [Bug 1609898] Re: dhclient incorrectly assumes a /64 ipv6 prefix

2016-09-15 Thread Dan Streetman
** Also affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Changed in: network-manager (Ubuntu Precise) Status: New => Invalid ** Patch added: "debdiff to fix network manager test in trusty"