(In reply to Luiz Pegoraro from comment #29)
> I am still wondering if the issue is on wpa_supplicant or on the hardware,
> because I know a guy who has another PC using Fedora 22 with wpa_supplicant
> 2.4 that connects in the network via NetworkManager.
> Also that configuration of the phase1, Can I set somewhere in the
> NetworkManager so I don't have to run command lines to connect to the
> network?
I got it working (F23/wpa_supplicant-2.4-7/openssl-1.0.2d-2) with a custom wpa_supplicant config and some manual steps:
network={
ssid="corpwifi"
key_mgmt=WPA-EAP
eap=PEAP
phase1="peaplabel=auto tls_disable_tlsv1_2=1"
phase2="auth=MSCHAPV2"
identity="***"
password="***"
}
Unfortunately, I couldn't get the above working with the Networkmanager (/etc/wpa_supplicant/wpa_supplicant.conf and ifcg-corpwifi). The config set in /etc/wpa_supplicant/wpa_supplicant.conf wasn't used.
(In reply to Luiz Pegoraro from comment #29)
> I am still wondering if the issue is on wpa_supplicant or on the hardware,
> because I know a guy who has another PC using Fedora 22 with wpa_supplicant
> 2.4 that connects in the network via NetworkManager.
For F22 with wpa_supplicant 2.4 check this bug too, it seems the openssl library version matters: https:/ /bugzilla. redhat. com/show_ bug.cgi? id=1276073
> Also that configuration of the phase1, Can I set somewhere in the
> NetworkManager so I don't have to run command lines to connect to the
> network?
I got it working (F23/wpa_ supplicant- 2.4-7/openssl- 1.0.2d- 2) with a custom wpa_supplicant config and some manual steps: "peaplabel= auto tls_disable_ tlsv1_2= 1" "auth=MSCHAPV2" supplicant/ wpa_supplicant. conf and ifcg-corpwifi). The config set in /etc/wpa_ supplicant/ wpa_supplicant. conf wasn't used.
network={
ssid="corpwifi"
key_mgmt=WPA-EAP
eap=PEAP
phase1=
phase2=
identity="***"
password="***"
}
Unfortunately, I couldn't get the above working with the Networkmanager (/etc/wpa_