I assume you mean these 2 failing tests, below; that's correct behavior
now, the tests should be changed to expect a /128 DHCPv6 address instead
of a /64 DHCPv6 address.
======================================================================
FAIL: test_open_b_ip6_dhcp (__main__.T)
Open network, 802.11b, IPv6 with DHCP
----------------------------------------------------------------------
Traceback (most recent call last):
File
"/tmp/autopkgtest.O8S7lL/build.sFx/network-manager-1.2.0/debian/tests/wpa-dhclient",
line 55, in test_open_b_ip6_dhcp
['11.0'])
File
"/tmp/autopkgtest.O8S7lL/build.sFx/network-manager-1.2.0/debian/tests/wpa-dhclient",
line 149, in do_test
self.check_address(ipv6)
File
"/tmp/autopkgtest.O8S7lL/build.sFx/network-manager-1.2.0/debian/tests/wpa-dhclient",
line 228, in check_address
self.assertRegex(out, 'inet6 2600::[0-9a-z]+/64')
AssertionError: Regex didn't match: 'inet6 2600::[0-9a-z]+/64' not found in
'20: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group
default qlen 1000\n link/ether 02:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff\n
inet6 2600::11/128 scope global tentative \n valid_lft forever
preferred_lft forever\n inet6 fe80::ff:fe00:0/64 scope link \n
valid_lft forever preferred_lft forever\n'
======================================================================
FAIL: test_wpa2_ip6 (__main__.T)
WPA2, 802.11g, IPv6
----------------------------------------------------------------------
Traceback (most recent call last):
File
"/tmp/autopkgtest.O8S7lL/build.sFx/network-manager-1.2.0/debian/tests/wpa-dhclient",
line 137, in test_wpa2_ip6
'Authentication suites: PSK'])
File
"/tmp/autopkgtest.O8S7lL/build.sFx/network-manager-1.2.0/debian/tests/wpa-dhclient",
line 149, in do_test
self.check_address(ipv6)
File
"/tmp/autopkgtest.O8S7lL/build.sFx/network-manager-1.2.0/debian/tests/wpa-dhclient",
line 228, in check_address
self.assertRegex(out, 'inet6 2600::[0-9a-z]+/64')
AssertionError: Regex didn't match: 'inet6 2600::[0-9a-z]+/64' not found in
'45: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group
default qlen 1000\n link/ether 02:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff\n
inet6 2600::12/128 scope global tentative \n valid_lft forever
preferred_lft forever\n inet6 fe80::ff:fe00:0/64 scope link \n
valid_lft forever preferred_lft forever\n'
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
https://bugs.launchpad.net/bugs/1609898
Title:
dhclient incorrectly assumes a /64 ipv6 prefix
Status in isc-dhcp package in Ubuntu:
Fix Committed
Status in isc-dhcp source package in Precise:
Fix Committed
Status in isc-dhcp source package in Trusty:
Fix Committed
Status in isc-dhcp source package in Xenial:
Fix Committed
Status in isc-dhcp source package in Yakkety:
Fix Committed
Status in isc-dhcp package in Debian:
Fix Released
Bug description:
[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 other systems are not
on-link. This /64 assumption of dhclient effectively breaks the
client networking for certain addresses.
[Test Case]
Set up a server with two interface nics, and one client connected to
each of those interfaces. On the server, set up a ipv6 subnet on each
interface, with a larger prefix than /64, e.g.:
2001:db8:0:0:1::/96
2001:db8:0:0:2::/96
configure dhcpv6 on the server, to provide ipv6 addresses on each
interface. Set the server as the default ipv6 route for the clients.
Allow the clients to get dhcpv6 ipv6 addresses from the server. The
clients will each get a ipv6 address with a /64 prefix, due to the bug
in dhclient.
Try to ping (or otherwise communicate) between the clients. Since
they have /64 prefixes, they think they are on-link with each other,
but they are not, so they can't communicate.
After the dhclient bug is fixed, repeat the above setup, and the
clients will get /128 prefixes instead, and then will be able to
communicate with each other, because they will route the traffic to
each other through the server.
[Regression potential]
None. Non-standard (i.e. not /64) subnets served by dhcpv6 currently
are broken, this fixes that.
[Other info]
This is fixed in debian:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=684009
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1609898/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
