Well, that would cover the first failure mode I described, but we experience
the second one.
I don't see any workaround, apart from removing the -1 from the dhclient
options.
I'm sorry, but this means that a _part_ of my report might be invalid
(though we think we saw that issue), but the other part is valid, unless
you can provide instructions how to not experience this issue.
When an interface is set to use dhcp and is set to an online state,
dhclient shouldn't give up retrying to renew a lease, but it does.
** Changed in: ifupdown (Ubuntu)
Status: Invalid => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1196975
Title:
ifupdown calling dhclient with -1 causes it to fail when dhcp server
unavailable
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1196975/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
