Comment 167 for bug 272185

Revision history for this message
Omer (omer-qadir) wrote :

hello,

I am guessing this isn't resolved yet. My experience is as follows.
Hardware => Gateway M280, intel pro 2200
Connecting to Eduroam => WPA-EAP, TKIP, PEAP, MSCHAPV2 (Uni of York)

NM just doesn't work. I have been attempting off and on for the past month now and it hasn't connected once. I just tried the PPA updates and that didn't work either. Same result, just takes a little longer. Manually starting wpa_supplicant works, but intermittently. A successfull connection, if established, occurs within apprx 2 seconds.

wpa_supplicant.conf :

ap_scan=1
ctrl_interface=/var/run/wpa_supplicant
network={
ssid="eduroam"
# scan_ssid=1
proto=WPA
key_mgmt=WPA-EAP
pairwise=TKIP
group=TKIP
eap=PEAP MSCHAPV2
identity="xxx"
password="xxx"
# ca_cert="/etc/ssl/certs/ca.pem"
# ca_cert2="/etc/ssl/certs/ca.pem"
# phase1="peaplabel=0"
phase2="auth=MSCHAPV2"
# eapol_flags=0
}

After stopping NM, I connect using :
sudo wpa_cli -i eth1 terminate; sudo wpa_supplicant -i eth1 -dd -B -D wext -c /etc/wpa_supplicant/wpa_supplicant.conf -f /var/log/wpa_supplicant.log

and keep repeating this untill I get a connection - on average once out of 10 attempts.

I have lots of logs for successull and failed attempts. Attaching 2 samples each (with some bits removed)

What I have noticed is that it always get to the phase 2 (MSCHAPV2 succeeds). When the connection fails, the machine seems to repeatedly receive the same packet during the 4-way handshake (Pairwise Install ACK MIC). At other times, it just magically receives the next packet as well. Something wrong with key sync maybe?

Sitting right next to the wireless hub didn't help.

any experiments you want done, just lemme know... I am desperate to get this working. extremely frustrated.

Thanks
Omer