Take the 2-minute tour ×
Unix & Linux Stack Exchange is a question and answer site for users of Linux, FreeBSD and other Un*x-like operating systems.. It's 100% free, no registration required.

I've been profiling my boot times with bootchart and it seems that wpa_supplicant and dhcp take a significant amount of time during the boot process to get up and running and associate with my home router.

Here is my /etc/network/interfaces:
auto lo

iface lo inet loopback
iface eth0 inet dhcp

allow-hotplug wlan0
auto wlan0

iface wlan0 inet dhcp
    wpa-ssid "ssid"
    wpa-psk "password"

The connection works fine - it just takes awhile.

I'm interested in optimizing boot time and don't need network until later. How can I delay the authentication process for WiFi until after I've started X and the system has booted?

Here is my bootchart: enter image description here

share|improve this question

1 Answer 1

The easiest way would be to take your WiFi config out of /etc/network/interfaces or similar and switch to Network Manager. Even if you set the connection to a system connection, it should be brought up in the background. This also gives you much easier WiFi connection management, at least for laptops that may be moving between networks.

You could also take out the auto or allow-hotplug line for your WiFi card, and instead bring it up later (either by hand, or by adding an init script that does an ifup on it). You need not have that init script block starting your display manager.

Of course, if you're running any services that actually require an Internet connection to start, they'll fail. You can work around this with the custom init script approach, as you can add dependencies to those services.

share|improve this answer

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.