2

I've seen a few post similar to this, but I still have the network unreachable.

How do I bring up my wireless network at boot?

"Waiting for network configuration" adding 3 to 5 minutes to boot time

I can't reinstall because I have mysql databases in the system.

I don't know what any other thing I can do.

Thanks.

/etc/network/interfaces

#The loopback network interface
auto lo
iface lo inet loopback

# The primary network interface
auto wlan0
iface wlan0 inet dhcp
wpa-ssid xxxxxxx
wpa-psk xxxxxxxx
Community
  • 1
Antonio Sánchez
  • 635

3 Answers3

4

I suspect that (sadly) the second thread you posted has the answer. It seems now that the /etc/network/interfaces file contains the interfaces that have to be brought up necessarily by the system, while network-manager is in charge of "non system-critical" interfaces.

So the "best practice" now seems to be to leave empty the /etc/network/interfaces file and set your interfaces inside network-manager.

However, if for any reason you don't like this approach (e.g. I don't like it) there could be another not-so-clean solution. You could edit your /etc/init/failsafe.conf file and comment-out the two sleep of 40 and 59 seconds. This will make your Ubuntu boot faster, but you can't take it for granted that you will have your network interfaces up at the end of the boot process.

Community
  • 1
Avio
  • 3,098
2

Yes the same happened to me when I installed Ubuntu 12.04.1 Server + no-install-recommends ubuntu-desktop on two Lenovo IBM Thinkpads. I also got “waiting for network configuration” and network down messages and I was totally unable to get the wireless adaptor working.

However the fix for me was to make the /etc/network/interfaces file as simple as possible. I changed it to only use three lines:

#The loopback network interface
auto lo
iface lo inet loopback

Ubuntu then starts up really quickly with no delays. The eth0 adapter starts automatically and I then configure the wlan0 wireless network via Network Connections.

Cheers

P.S. Unity is brilliant for quick keyboard navigation around a GUI screen. Canonical have really raised the bar.

Dig
  • 341
1

Refresh your MAC address using Virtual Box machine settings and remove the kernel’s networking interface rules file so that it can be regenerated:

sudo rm -f /etc/udev/rules.d/70-persistent-net.rules sudo reboot

It will work for your clone VM.

Val Luis
  • 11