Hello Dan, or anyone else affected, Accepted isc-dhcp into trusty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/isc- dhcp/4.2.4-7ubuntu12.9 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: isc-dhcp (Ubuntu Trusty) Status: In Progress => Fix Committed ** Tags added: verification-needed -- 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/1689854 Title: Multiple DHCPv6 client interfaces fail to receive some server responses Status in isc-dhcp package in Ubuntu: Fix Released Status in isc-dhcp source package in Trusty: Fix Committed Bug description: [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. * This is fixed upstream already, and the patch is included in Xenial and later releases. This patch is needed only in the Trusty release. * Upstream patch : https://source.isc.org/cgi-bin/gitweb.cgi?p=dhcp.git;a=commit;h=4b8251a0c06b7d8706a28904fdef2414f045cc2c [Other Info] * [ISC-Bugs #34784] Please note that no ISC bug URL can be provided since the ISC bug database is closed : Reference: https://www.isc.org/community/report-bug/ ... Confidentiality It is typical for open-source projects to have an open bug database. At the moment, the ISC bug database is closed. However, we reserve the right to publish your bug report at some point in the future. Please do not include information you consider to be confidential. ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1689854/+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
