Public bug reported:
I have a home network with WPA and broadcast SSID enabled. I want my
Ubuntu Hardy machine to connect to this network automatically on boot.
I declared the following in /etc/network/interfaces:
auto ath0
iface ath0 inet static
mtu 1400
address 192.168.0.3
netmask 255.255.255.0
gateway 192.168.0.254
wpa-driver madwifi
wpa-ssid boboli
wpa-key-mgmt WPA-PSK
wpa-psk "XXXX"
The machine is supposed to come up with a static IP on the "boboli"
network. However, right after boot, wpa_supplicant is running, but my
wireless card is associated with an open network in the neighborhood and
is not connected to my preferred SSID.
Using wpa_cli I get:
% sudo wpa_cli
> status
wpa_state=INACTIVE
ip_address=192.168.0.3
I have to bring the interface down, remove the ath_pci module, and bring
everything back up in order to connect to the network. After running
these commands I am back on the correct network:
% sudo ifdown ath0
% sudo modprobe -r ath_pci
% sudo modprobe ath_pci
% sudo ifup ath0
Removing and reinserting the ath_pci module is necessary due to a
different bug, reported elsewhere. (It fails to associate all but the
first time it is used after the module has been loaded.)
The problem I am reporting here is that the network connection should
work right after boot; I should not have to restart networking in order
to get it to work on boot.
** Affects: ubuntu
Importance: Undecided
Status: New
--
madwifi/ath_pci does not connect to wpa network on boot
https://bugs.launchpad.net/bugs/280248
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
