[Bug 1447715] Re: dhclient -6: Can't bind to dhcp address: Cannot assign requested address

[Dan Streetman]

This is fixed in debian ifupdown 0.8.11 by this patch:
--- ifupdown-0.8.10/wait-for-ll6.sh	2015-12-01 16:50:26.000000000 -0500
+++ ifupdown-0.8.11/wait-for-ll6.sh	2016-04-20 08:57:37.000000000 -0400
@@ -4,7 +4,7 @@
 delay=${IF_LL_INTERVAL:-0.1}
 
 for attempt in $(seq 1 $attempts); do
-	lladdress=$(ip -6 -o a s dev "$IFACE" scope link)
+	lladdress=$(ip -6 -o a s dev "$IFACE" scope link -tentative)
 	if [ -n "$lladdress" ]; then
 		attempt=0
 		break


** Also affects: ifupdown (Ubuntu)
   Importance: Undecided
       Status: New

** Changed in: isc-dhcp (Ubuntu)
       Status: Confirmed => Invalid

** No longer affects: isc-dhcp (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to isc-dhcp in Ubuntu.
https://bugs.launchpad.net/bugs/1447715

Title:
  dhclient -6: Can't bind to dhcp address: Cannot assign requested
  address

Status in DHCP:
  New
Status in ifupdown package in Ubuntu:
  New

Bug description:
  After upgrading to Ubuntu 15.04 my computer is unable to obtain an
  IPv6 address via DHCPv6. The root cause is that dhclient is exiting
  with the following message:

  -----------------------------------------------------
  Can't bind to dhcp address: Cannot assign requested address
  Please make sure there is no other dhcp server
  running and that there's no entry for dhcp or
  bootp in /etc/inetd.conf.   Also make sure you
  are not running HP JetAdmin software, which
  includes a bootp server.

  If you think you have received this message due to a bug rather
  than a configuration issue please read the section on submitting
  bugs on either our web page at www.isc.org or in the README file
  before submitting a bug.  These pages explain the proper
  process and the information we find helpful for debugging..

  exiting.
  -----------------------------------------------------

  The problem seems to exist in isc-dhcp-client 4.3.1-5ubuntu2 (15.04
  version) because downgrading to isc-dhcp-client 4.2.4-7ubuntu14 (14.10
  version) allows me to obtain an address.

  NetworkManager is the one launching dhclient. The two invocations (one
  for IPv4 and one for IPv6) are:

  dhclient_start(): running: /sbin/dhclient -d -q -sf
  /usr/lib/NetworkManager/nm-dhcp-helper -pf /run/sendsigs.omit.d
  /network-manager.dhclient-eth0.pid -lf /var/lib/NetworkManager
  /dhclient-c0a3dfde-5c0b-4cef-9c3b-563cfb1fb9d2-eth0.lease -cf
  /var/lib/NetworkManager/dhclient-eth0.conf eth0

  dhclient_start(): running: /sbin/dhclient -d -q -6 -N -sf
  /usr/lib/NetworkManager/nm-dhcp-helper -pf /run/sendsigs.omit.d
  /network-manager.dhclient6-eth0.pid -lf
  /var/lib/NetworkManager/dhclient6-c0a3dfde-5c0b-4cef-9c3b-
  563cfb1fb9d2-eth0.lease -cf
  /var/lib/NetworkManager/dhclient6-eth0.conf eth0

  I do not see anything suspicious with the way both dhclients are
  invoked.

  Given that a downgrade allows me to obtain an IPv6 address I think
  this might be a bug in the ISC DHCP client rather than in
  NetworkManager.

To manage notifications about this bug go to:
https://bugs.launchpad.net/dhcp/+bug/1447715/+subscriptions