touch-packages team mailing list archive
-
touch-packages team
-
Mailing list archive
-
Message #135096
[Bug 1543352] [NEW] inet6 dhcp doesn't wait for link-local address to leave tentative - dhclient fails to bind
Public bug reported:
=
Description: Ubuntu Xenial Xerus (development branch)
Release: 16.04
ifupdown:
Installed: 0.8.10ubuntu1
Candidate: 0.8.10ubuntu1
=
With an /etc/network/interfaces file containing:
auto eno16780032
iface eno16780032 inet dhcp
iface eno16780032 inet6 dhcp
On boot, ifup starts 'dhclient -6' before the link local address has
completed Duplicate Address Discovery (the address is marked
'tentative'). In turn, dhclient reports 'Can't bind to dhcp address:
Cannot assign requested address', and fails almost immediately.
It would seem that either wait-for-ll6.sh should wait for the link local
address to come up AND stop being tentative, or the dhcp method for
inet6 should call settle-dad.sh after wait-for-ll6?
This is partly a race condition, so on slower devices the dad may
complete by the time dhclient has got started, however I can regularly
reproduce this on a virtual machine.
** Affects: ifupdown (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ifupdown in Ubuntu.
https://bugs.launchpad.net/bugs/1543352
Title:
inet6 dhcp doesn't wait for link-local address to leave tentative -
dhclient fails to bind
Status in ifupdown package in Ubuntu:
New
Bug description:
=
Description: Ubuntu Xenial Xerus (development branch)
Release: 16.04
ifupdown:
Installed: 0.8.10ubuntu1
Candidate: 0.8.10ubuntu1
=
With an /etc/network/interfaces file containing:
auto eno16780032
iface eno16780032 inet dhcp
iface eno16780032 inet6 dhcp
On boot, ifup starts 'dhclient -6' before the link local address has
completed Duplicate Address Discovery (the address is marked
'tentative'). In turn, dhclient reports 'Can't bind to dhcp address:
Cannot assign requested address', and fails almost immediately.
It would seem that either wait-for-ll6.sh should wait for the link
local address to come up AND stop being tentative, or the dhcp method
for inet6 should call settle-dad.sh after wait-for-ll6?
This is partly a race condition, so on slower devices the dad may
complete by the time dhclient has got started, however I can regularly
reproduce this on a virtual machine.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1543352/+subscriptions
Follow ups