Steve,
Good sleuthing.
Bug 974284 has good info in it.
This is definitely tricky.
I think we have the following cases to consider and may be at odds.
a.) dhclient -1 should exit failure as documented.
b.) we need a reliable point in boot where all static networking is configured.
c.) Ill timed
Here is the behavior on either 14.04 or 16.04:
# dhclient -1 -v virbr0
Internet Systems Consortium DHCP Client 4.2.4
Copyright 2004-2012 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/
Listening on LPF/virbr0/52:54:00:05:e1:f3
Sending
According to the bzr history in lp:ubuntu/wily/isc-dhcp, this patch is
related to bug #974284:
committer: Stéphane Graber
branch nick: isc-dhcp
timestamp: Wed 2012-09-12 17:30:23 -0400
message:
Set onetry = 0 early enough to actually work. (LP: #974284)
And Scott, you
** Changed in: isc-dhcp (Ubuntu)
Importance: Undecided => Medium
** 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/1633619
Title:
for reference, you can make it fail faster like this in
/etc/dhcp/dhclient.conf
timeout 3;
retry 3;
#reboot 10;
select-timeout 5;
initial-interval 1;
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.