and works perfectly. However, when I enter the same info into NetworkManager, it tries but eventually gives up.
One thing I noticed is that without the option:
pairwise=TKIP
It would not work. I do not know how to investigate what parameters NM is passing to wpa_supplicant, but if it omits that one, things will probably not work.
This would be a wonderful fix to have, since doing this manually requires I kill NM and do it myself instead, not preferable.
I can confirm this.
I spent the better part of today trying to connect to my University's TTLS network before figuring it out via wpa_supplicant.
Here is my wpa_supplicant configuration:
ctrl_interface_ group=0 /var/run/ wpa_supplicant
ssid=" My-SSID"
key_mgmt= WPA-EAP
pairwise= TKIP
ca_cert= "/tmp/rootca. cer"
identity= "<username> "
password= "<password> "
phase2= "auth=PAP"
ctrl_interface=
eapol_version=1
ap_scan=1
fast_reauth=1
network={
proto=WPA
group=TKIP
eap=TTLS
priority=2
}
It is run with:
sudo wpa_supplicant -D wext -i ath0 -c /etc/wpa_ supplicant/ supp.conf
and works perfectly. However, when I enter the same info into NetworkManager, it tries but eventually gives up.
One thing I noticed is that without the option:
pairwise=TKIP
It would not work. I do not know how to investigate what parameters NM is passing to wpa_supplicant, but if it omits that one, things will probably not work.
This would be a wonderful fix to have, since doing this manually requires I kill NM and do it myself instead, not preferable.