I vaguely remember discussing that on IRC already, but there it's again
anyway ;)
I don't agree that we should start dhclient in the background on failure
to get an IP, that sounds wrong and will prevent any of the ifupdown
scripts from running properly, not to mention confuse ifupdown regarding
the state of the interface.
What I did fix last cycle with a change to isc-dhcp is the case where
you boot with a working dhcp config and then your dhcp server dies for a
few days. In the past, dhclient would exit and you'd never get an IP
again, now that's fixed and dhclient will never exit once it
successfully gets a first lease.
In your weird setup, I see two obvious options:
- Go with static addressing
- Go with a manual interface entry calling "dhclient $INTERFACE" as post-up
I'm going to mark it as won't fix based on that, if you don't agree,
feel free to revert or poke me on IRC :)
** Changed in: ifupdown (Ubuntu)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1017166
Title:
Unplugged or deactivated ethernet interfaces may not be handled
properly
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1017166/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
