This bug was fixed in the package ifupdown - 0.8.10ubuntu1.3
---
ifupdown (0.8.10ubuntu1.3) xenial; urgency=medium
[ Wido den Hollander ]
* Wait properly for Link-Local Address to go through DAD.
(LP: #1447715)
-- Dan Streetman Tue, 17 Apr 2018 17:29:54
-0400
** Changed i
Xenial verification:
ubuntu@lp1447715:/etc/network/interfaces.d$ dpkg -l | grep ifupdown
ii ifupdown 0.8.10ubuntu1.2
amd64high level tools to configure network interfaces
ubuntu@lp1447715:/etc/network/interfaces.d$ grep -A 2 ens7 50-cl
Hello Eloy, or anyone else affected,
Accepted ifupdown into xenial-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/ifupdown/0.8.10ubuntu1.3 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://
** Description changed:
[Impact]
When using dhcpv6 configured via ifupdown, the interface's dhcp client
fails to start at boot with the error:
Can't bind to dhcp address: Cannot assign requested address
This is because ifupdown doesn't wait, after bringing the interface up,
fo
** Patch removed: "lp1447715-xenial.debdiff"
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1447715/+attachment/4745626/+files/lp1447715-xenial.debdiff
** Patch added: "lp1447715-xenial.debdiff"
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1447715/+attachment/5120139/+f
Test build in ppa:
https://launchpad.net/~ddstreet/+archive/ubuntu/lp1447715
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1447715
Title:
dhclient -6: Can't bind to dhcp address: Cannot assign reque
i opened bug 1764478 to change dhclient 'stateless' mode, but as
explained in that bug, it's better to fix ifupdown, here.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1447715
Title:
dhclient -6: C
I'm re-opening this for Xenial, moving from Wontfix back to in progress.
This is because while 'normal' dhcpv6 works without this fix because of
the patch to dhclient (see my explanation in comment 23), there is a
special case of using dhclient in 'stateless' mode, i.e. dhclient -6 -S.
In that mode
** Tags removed: sts-sru
** Tags added: sts-sru-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1447715
Title:
dhclient -6: Can't bind to dhcp address: Cannot assign requested
address
To manag
Thank you Dan, for the analysis. Per comment #23, I'll mark Won't Fix
for xenial.
** Changed in: ifupdown (Ubuntu Xenial)
Status: In Progress => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.
for NetworkManager, this is fixed starting in wily (see comment 13) and
so should work in xenial/yakkety; and in trusty, dhclient still works
(per description stating dhclient works in isc-dhcp-client
4.2.4-7ubuntu14). I'm not sure if NetworkManager using dhcpv6 works in
precise (but who is using
Martin, I'm not sure.
I just realized that the original report shows a dhclient line of
/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-eth
** Description changed:
[Impact]
When using dhcpv6 configured via ifupdown, the interface's dhcp client
fails to start at boot with the error:
Can't bind to dhcp address: Cannot assign requested address
This is because ifupdown doesn't wait, after bringing the interface up,
fo
bug 1633479 actually was released to -updates now, so is there still
actually some observable behaviour difference that can be used to both
justify and verify this update?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.la
update for this:
this patch is already included upstream in debian, and is already
included in yakkety. It's not yet in xenial. It's not required in
trusty (bug doesn't exist there).
additionally, bug 1633479 (which fixes this by putting the DAD wait in
isc-dhcp-client) is in proposed for p/t/x
** Tags added: sts-sponsor
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1447715
Title:
dhclient -6: Can't bind to dhcp address: Cannot assign requested
address
To manage notifications about this
> The use case I found was in initramfs-tools, which recently SRU'd a change
> that uses dhclient to
> support 'ip=' command lines and dhcpv6.
aha, and busybox ip doesn't support the -tentative param that the
ifupdown change uses.
+1 on fixing isc-dhcp then (as well as leaving this fix in ifupdo
Dan,
The use case I found was in initramfs-tools, which recently SRU'd a change that
uses dhclient to support 'ip=' command lines and dhcpv6.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1447715
Tit
> The fix i intended was to dhclient, so that dhclient would wait in
PREINIT6 dhclient-script.
Looks good to me, fixing dhclient as well is a good idea.
> I think that is generally more functional as it would mean ifupdown or any
> other user of dhclient
> would get the fix.
What other users ar
I found this bug separately and filed bug 1633479.
The fix i intended was to dhclient, so that dhclient would wait in PREINIT6
dhclient-script.
I think that is generally more functional as it would mean ifupdown or
any other user of dhclient would get the fix.
Thoughts?
--
You received this bu
** Changed in: ifupdown (Debian)
Status: Unknown => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1447715
Title:
dhclient -6: Can't bind to dhcp address: Cannot assign requested
** Project changed: ifupdown => ubuntu-translations
** Changed in: ubuntu-translations
Importance: Unknown => Undecided
** Changed in: ubuntu-translations
Status: Fix Released => New
** Changed in: ubuntu-translations
Remote watch: Debian Bug tracker #834928 => None
** No longer affe
** Changed in: ifupdown
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1447715
Title:
dhclient -6: Can't bind to dhcp address: Cannot assign requested
address
To
And yakkety has ifupdown 0.8.13 which contains the fix already.
** Tags added: sts-sru
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1447715
Title:
dhclient -6: Can't bind to dhcp address: Cannot a
I tested on precise and trusty, and this problem doesn't appear there,
so only xenial requires the ifupdown SRU.
** Changed in: ifupdown (Ubuntu Trusty)
Status: In Progress => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubu
** Changed in: ifupdown (Ubuntu Xenial)
Assignee: (unassigned) => Dan Streetman (ddstreet)
** Changed in: ifupdown (Ubuntu Precise)
Assignee: (unassigned) => Dan Streetman (ddstreet)
** Changed in: ifupdown (Ubuntu Trusty)
Assignee: (unassigned) => Dan Streetman (ddstreet)
** Chan
** Also affects: ifupdown (Ubuntu Precise)
Importance: Undecided
Status: New
** Also affects: ifupdown (Ubuntu Trusty)
Importance: Undecided
Status: New
** Also affects: ifupdown (Ubuntu Xenial)
Importance: Undecided
Status: New
--
You received this bug notificatio
** Description changed:
- 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:
+ (Original bug description follows SRU info)
+
+ [Description]
+
+ When using dhcpv6 configured via if
This is also fixed in network-manager upstream
(git://git.freedesktop.org/git/NetworkManager/NetworkManager.git) by
commit d1295b12e9f802867edef57ee02c87495df1683e ("dhcp: wait for an
IPv6LL address before starting DHCPv6 (bgo #740147)") which is included
in Ubuntu network-manager starting in wily.
The attachment "lp1447715-xenial.debdiff" seems to be a debdiff. The
ubuntu-sponsors team has been subscribed to the bug report so that they
can review and hopefully sponsor the debdiff. If the attachment isn't a
patch, please remove the "patch" flag from the attachment, remove the
"patch" tag, a
** Patch added: "lp1447715-xenial.debdiff"
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1447715/+attachment/4745626/+files/lp1447715-xenial.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.n
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.0 -0500
+++ ifupdown-0.8.11/wait-for-ll6.sh 2016-04-20 08:57:37.0 -0400
@@ -4,7 +4,7 @@
delay=${IF_LL_INTERVAL:-0.1}
for attempt in $(seq 1 $attempts); do
-
Better yet, have dhclient retry that bind call itself, at least for a
short while, before throwing an error.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1447715
Title:
dhclient -6: Can't bind to d
** Changed in: dhcp
Status: Unknown => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1447715
Title:
dhclient -6: Can't bind to dhcp address: Cannot assign requested
address
To manage n
** Bug watch added: Debian Bug tracker #834928
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=834928
** Also affects: dhcp via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=834928
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a mem
This is still an issue in Ubuntu Server 16.04.1. I have the following in
my /etc/network/interfaces file:
# The primary network interface
auto ens3
iface ens3 inet dhcp
# This is an autoconfigured IPv6 interface
iface ens3 inet6 auto
dhcp 1
And on startup:
Aug 5 15:55:23 flounder dhclient[24
But this worked:
iface enp0s3 inet6 auto
iface enp0s3 inet6 dhcp
pre-up sleep 10
But a gross ugly hack...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1447715
Title:
dhclient -6: Can't bind t
OK, the last comment was a bit premature. After rebooting another time
or two, it seems that disable_dad did NOT help for me. Still happens
sometimes on boot.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net
I can confirm that IPv6 on Ubuntu 15.10 is basically broken out of the
box... at least, the DHCPv6 is broken out of the box due to this issue.
The workaround of setting disable_dad worked for me, described at
https://www.agwa.name/blog/post/beware_the_ipv6_dad_race_condition
--
You received this
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: isc-dhcp (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1447715
Title:
d
Better explained here:
https://www.agwa.name/blog/post/beware_the_ipv6_dad_race_condition
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1447715
Title:
dhclient -6: Can't bind to dhcp address: Cannot
I understand that binding to ipv6 addresses that haven't finished
Duplicate Address Detection causes the bind() to fail.
http://www.freedesktop.org/wiki/Software/systemd/NetworkTarget/ suggests
using IP_FREEBIND:
IP_FREEBIND (since Linux 2.4)
If enabled, this boolean option a
A quick update -- This seems to be a timing issue, i.e. dhclient trying
to bind to the DHCPv6 port (UDP 546) on a link-local address when the
interface is not ready, but I am not sure. What I do know is that the
following patch to isc-dhcp-client 4.3.1 works around the problem:
--- a/common/socket
43 matches
Mail list logo
