Fedora 7 broke the automatic ath0/wpa_supplicant startup. It is still possible to get the network working by restarting wpa_supplicant, doing an ifconfig down/up on ath0, and then restarting ntpd (which fails in a way that causes it not to recover). Does anyone have fedora-7 booting with an automatic wpa wifi connection yet? What is the secret?
In fact, just some insight into what is going on with wpa_supplicant would be appreciated. Under fc6 (and fc5) one could start wpa_supplicant before the network startup and have ath0 correctly associate with the AP. Now starting wpa_supplicant just before the network startup causes it to retry associating in an infinite loop with no success. Restarting it via "service wpa_supplicant restart " causes it to associate immediately.
-wolfgang
"Wolfgang S. Rupprecht" wolfgang.rupprecht+gnus200706@gmail.com writes:
Fedora 7 broke the automatic ath0/wpa_supplicant startup. It is still possible to get the network working by restarting wpa_supplicant, doing an ifconfig down/up on ath0, and then restarting ntpd (which fails in a way that causes it not to recover). Does anyone have fedora-7 booting with an automatic wpa wifi connection yet? What is the secret?
Playing around it seems that the only way to keep wpa_supplicant happy is to start it after the interface is brought up but before dhclient is started on the interface. The simplest way to hack this was to put this at the end of /etc/sysconfig/network-scripts/ifup-wireless:
# wsrcc hack start if [ ! -S /var/run/wpa_supplicant/$DEVICE ] then wpa_supplicant -c /etc/wpa_supplicant/wpa_supplicant.conf -i$DEVICE -Dmadwifi -B fi # wsrcc end end
That did the trick and the ath0 now starts up faster in F7 than it did under FC6. Hardwiring "madwifi" is obviously grotty, but this is just a proof of concept.
-wolfgang
-
Wolfgang S. Rupprecht