Red Hat Bugzilla – Bug 444095
wpa_supplicant fails to connect to uni wifi AP
Last modified: 2008-08-19 14:46:39 EDT
I am trying to connect to my Uni's wifi using the following wpa_supplicant.conf:
On Ubuntu 8.04 (wpa_supplicant 0.5.9 and 2.6.24 kernel) the above
wpa_supplicant.conf works. I tried the wpa_supplicant from FC8 (0.5.10) but
still no go. I have an Intel Corporation PRO/Wireless 3945ABG card with iwl3945
so some additional comments; I have wpa_supplicant detailed logs for both
Ubuntu, F9 + wpa_supplicant 0.5.10, and F9 + wpa_supplicant 0.6.3 sent to me by
the bug filer and can provide them if needed.
The problem appears to be that the driver keeps sending disconnect events at
inopportune times. There are a ton more disconnect events with F9 than with
Ubuntu, and the fact that both wpa_supplicnat 0.5.10 and 0.6.3 show the same
symptoms indicates that it's more of a driver issue than a supplicant issue.
maybe install some debug kernels and enable debugging in modprobe.conf and get
some output as to why the driver sends the disconnects?
Changing version to '9' as part of upcoming Fedora 9 GA.
More information and reason for this action is here:
I originally had a lot of problems finding the correct form of the network block
to make a connection to my institution's wireless using peap with MSCHAPV2- I am
enclosing the lines below that I found worked for me eventually:
# York University eduroam network block
subject_match="/C=GB/L=York/O=University of York/OU=Computing
VeriSign/OU=Member, VeriSign Trust Network/CN=nasaaa1.york.ac.uk"
For me the proto and pairwise lines seemed to be needed before it would work.
Also I needed username@machinename rather than just username for the identity.
Might be worth trying in your case - it took me several months of fiddling
before I found the right combination of lines. Although this problem may have
other causes it would be worth ruling out a config file problem before chasing
The subject_match line is not essential but it does confirm security certificate
Do you continue to experience this problem with current kernels?
Closed due to lack of response...