[Bug 1196975] Re: ifupdown calling dhclient with -1 causes it to fail when dhcp server unavailable

[Sven Mueller]

This was previously marked incomplete, then expired. However, all the
information that is available is in the bug. Here is a summary again:

dhclient stops trying to renew a lease if a previous renewal failed (due
to server being unavailable).

See #6 for all the logs available. See how the client tried to renew,
then tried a new DHCPDISCOVER, then didn't try again for at least 3
hours, with expiry set to 4 hours or more and renewal time set to 2
hours.

This is a different scenario from the server not being available on
start, as clarified in #2.

Note that during the whole time, the client network interface was up, as
the switch it was connected to didn't fail.

** Changed in: ifupdown (Ubuntu)
       Status: Expired => New

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

Title:
  ifupdown calling dhclient with -1 causes it to fail when dhcp server
  unavailable

Status in “ifupdown” package in Ubuntu:
  New

Bug description:
  Present in the Precise version (0.7~beta2ubuntu8) at least:

  ifupdown is hardcoded to call dhclient with -1, which causes it to exit on the first failure.
  This can happen in two ways:
  1) Failure to bring up the interface if the dhcp server doesn't respond in time (default 60s).
  2) Failure to renew if the dhcp server was unavailable during a previous renewal try.

  This is http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=694541 as
  well, it seems.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1196975/+subscriptions