2

I have configured /etc/network/interface like this:

auto lo eth0
iface lo inet loopback
iface eth0 inet dhcp

But when a lease cannot be obtained, the booting is not completed. Is it possible to leave DHCP enabled but, in case a DHCP lease is not achieved, still complete the boot (so that a new network configuration can be performed)?

michelemarcon
  • 3,357
  • 10
  • 32
  • 37
  • 1
    This is not a reason for not completing the boot process. Maybe it gets long pauses when services (like mail) are waiting for dns resolver to timeout. In this case if you wait enough time the system will boot. Disable the boot splash screen or switch to console with ALT-F1 to see the booting messages. – forcefsck Apr 07 '11 at 12:15
  • What distribution is that, and what networking-related settings did you tune? – Gilles 'SO- stop being evil' Apr 07 '11 at 21:35
  • @Gilles Looks like Debian-based, probably Ubuntu. Still, should not be a reason for it to not boot, maybe just take longer. – penguin359 Apr 07 '11 at 23:19
  • Not Ubuntu, nor Debian. It is a customized busybox. – michelemarcon Apr 08 '11 at 09:39

1 Answers1

3

There is a undocumented parameter to udhcp which sends it to the background and allows to boot.

udhcpc -b
michelemarcon
  • 3,357
  • 10
  • 32
  • 37