wi-fi does not automatically come on during boot up

[nanjil]

I have installed hardy 8.04. When the computer boots up the network does not automatically come on. It requires a manual log in my a user.

my fiesty 7.04 has no such problem after modifying the /etc/network/interface file. If I do the same kind of modifications in hardy the network stops working

attached is the output of ifconfig -a (remembe ronly the wifi is on)

here is the default /etc/network/interfaces entry

auto lo
iface lo inet loopback

[Dariel Dato-on (odd-rationale)]

Try using /etc/rc.local to put the commands you need to connect to your network. e.g. "dhclient eth1"

rc.local is a script that runs on boot up. Be sure that it is executable.

[Ian Weisser (ian-weisser)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering is this still an issue for you? Can you try with latest Ubuntu release? Thanks in advance.

[pva (pieter-valkenburg)]

I have the same problem. I have use nfs to for my home and ldap to login. So I need networking before I login. If my laptop is wired it is no problem. But with wifi (wpa) and using networkmanager, I first have to login before wifi (wpa) can be enabled so I choose to configure wifi manual instead of roaming mode. After a reboot I can't login with my ldap/nfs account. Ldap is cached, but the home cannot be reached. So I do ctrl+alt+f1 and login to the console with a local account. With ipconfig i see that ath0 has a link local (169) address. With dhclient ath0 I don't get an proper IP address. I have to do a /etc/init.d/networking reload (or force-reload) to get an IP address for ath0. I log off and go to the x session (ctrl+alt+f7) and I can login with the ldap/nfs user.

As a workaround I put /etc/init.d/networking force-reload into /etc/rc.local but it isn't a need solution. Now I get an IP address from start, without switching to the console.

[Stavros Korokithakis (stavrosk)]

I am having the same problem with 8.10, I can access the wireless network fine after I log in, but before I do nothing comes up.

[Luke P. R. (siriusfox)]

I'm having this same problem with my Wired Network.

[Matteo Settenvini (tchernobog)]

I've added a link to: https://bugzilla.gnome.org/show_bug.cgi?id=603329
because I think it's relevant to this bug. Please tell me if I'm wrong, and I'll open a separate bug report on launchpad.

[Jeremy Nickurak (nickurak)]

This was an issue with earlier network-manager releases. Current network-manager allows you to edit a wireless network, and check the "availbale to all users" checkbox. If this is selected (on my lucid system), any network, including the WiFi, comes up on boot, bofer login.