** Description changed:
[Impact]
When using isc-dhcp-client on a Trusty system, with multiple interfaces
configured to use DHCPv6, not all the DHCPv6 clients will receive the
server responses on some of the interfaces. This results in not all
DHCPv6 interfaces being configured.
[Test Case]
Set up a DHCPv6 server with multiple interfaces (3-4 is enough) and
configure it to serve DHCPv6 on all the interfaces (as separate
subnets). The server release does not matter. Set up a client system
with the same number of interfaces, connected/bridged to the server
interfaces. The client must be a Trusty system. Configure (with
ifupdown via /etc/network/interfaces) all the interfaces to use DHCPv6,
and reboot. Keep rebooting until one or more of the DHCPv6 interfaces
fails to get an address; it should not take more than a few reboots.
After a failure, even manual ifdown/ifup on the failed interface will
not get a DHCPv6 address.
[Regression Potential]
As this changes how the isc-dhcp-client binds to IPv6 sockets, this
could cause problems when the client tries to bind, send, or receive,
with this or other operations.
+ Patch is already in most recent Ubuntu version :
+
+ artful --> isc-dhcp-4.3.5/RELNOTES: [ISC-Bugs #34784]
+ zesty --> isc-dhcp-4.3.5/RELNOTES: [ISC-Bugs #34784]
+ yakkety --> isc-dhcp-4.3.3/RELNOTES: [ISC-Bugs #34784]
+ xenial --> isc-dhcp-4.3.3/RELNOTES: [ISC-Bugs #34784]
+
[Other Info]
This is fixed upstream already, and the patch is included in Xenial and
later releases. This patch is needed only in the Trusty release.
** Changed in: isc-dhcp (Ubuntu)
Assignee: Dan Streetman (ddstreet) => (unassigned)
** Changed in: isc-dhcp (Ubuntu)
Status: In Progress => Fix Released
** Description changed:
[Impact]
When using isc-dhcp-client on a Trusty system, with multiple interfaces
configured to use DHCPv6, not all the DHCPv6 clients will receive the
server responses on some of the interfaces. This results in not all
DHCPv6 interfaces being configured.
[Test Case]
Set up a DHCPv6 server with multiple interfaces (3-4 is enough) and
configure it to serve DHCPv6 on all the interfaces (as separate
subnets). The server release does not matter. Set up a client system
with the same number of interfaces, connected/bridged to the server
interfaces. The client must be a Trusty system. Configure (with
ifupdown via /etc/network/interfaces) all the interfaces to use DHCPv6,
and reboot. Keep rebooting until one or more of the DHCPv6 interfaces
fails to get an address; it should not take more than a few reboots.
After a failure, even manual ifdown/ifup on the failed interface will
not get a DHCPv6 address.
[Regression Potential]
As this changes how the isc-dhcp-client binds to IPv6 sockets, this
could cause problems when the client tries to bind, send, or receive,
with this or other operations.
- Patch is already in most recent Ubuntu version :
+ Patch is already in most recent Ubuntu releases :
artful --> isc-dhcp-4.3.5/RELNOTES: [ISC-Bugs #34784]
zesty --> isc-dhcp-4.3.5/RELNOTES: [ISC-Bugs #34784]
yakkety --> isc-dhcp-4.3.3/RELNOTES: [ISC-Bugs #34784]
xenial --> isc-dhcp-4.3.3/RELNOTES: [ISC-Bugs #34784]
[Other Info]
This is fixed upstream already, and the patch is included in Xenial and
later releases. This patch is needed only in the Trusty release.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1689854
Title:
Multiple DHCPv6 client interfaces fail to receive some server
responses
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1689854/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
