Bugzilla – Bug 216063
Add phase2 auth support to [k]networkmanager
Last modified: 2008-01-31 12:51:56 UTC
I can connect to my institution AP's by manually invoking the wpa_supplicant with a wpa_supplicant.conf file from my institution. I can NOT connect using KnetworkManager directly (supplying the necessary info in the corresponding pop-up windows). Diving into log files, I see that the wpa_supplicant is invoked as manually (except for the conf file) and starts an endless tour of negotiation with accesible AP's till it exhausts its time). I can feed into Knetworkmanager almost all info the config file has, as far as acronyms are concerned(I am not expert): WPA-EAP, TTLS, WPA1. The conf file entries I do not find pop-up options for them are: phase2="auth=PAP",ap_scan=1,fast_reauth=1,priority=6. I do not know if this is a bug or just a lengthy negotiation. In any case: Would it be possible to force Knetwormanager to use my conf file? or Would it be possible to fill the (missing? )info in the knetworkmanagerrc file?. My (working) conf file is: # WPA conffiguration ctrl_interface=/var/run/wpa_supplicant #ctrol_interface_group=0 eapol_version=1 ap_scan=1 fast_reauth=1 network={ ssid="myssid" key_mgmt=WPA-EAP proto=WPA eap=TTLS anonymous_identity="anonymousidentity" identity="myidentity" password="mypasswrd" priority=6 phase2="auth=PAP" } Thanks a lot
Have you got this problem with 10.2?
(In reply to comment #1) > Have you got this problem with 10.2? > I have no access to any SUSE linux 10.2, if that is what you mean. All I know is that my SUSE linux 10.1 has the reported problem.
NetworkManager does not support phase2 authentication yet but somebody upstream is working on that issue.
Helmut, Timo: Are we updating NM to 0.6.5 for 10.3?
I have tested phase 2 support of NM 0.6.5 and nm-applet (network-manager-applet-0-6 branch) by fetching the patches from svn and applying to the latest nm src rpm from factory. I have also written a patch for knetworkmanager Patches for Networkmanger and Networkmanager-kde are attached. NM patches have been tested and are working fine, NM-kde patch has only been tested for compilation and running against wpa personal (no wpa enterprise at home ...)
Created attachment 142438 [details] Add phase2 support to NM (core) apply with %patchXX -p2
Created attachment 142439 [details] Add phase2 support to NM (gnome nm-applet) apply with (cd gnome/applet %patchXX -p3 )
Created attachment 142440 [details] Add phase2 support to NM (knetworkmanager) apply with %patchXX
*** Bug 230684 has been marked as a duplicate of this bug. ***
*** Bug 205479 has been marked as a duplicate of this bug. ***
Created attachment 142539 [details] Add phase2 support to NM (knetworkmanager) There was a small error in the ui file The patch(es) have been tested successfully with eduroam (www.eduroam.org) at RWTH Aachen, using PAP for phase2
The current svn version does list PAP for phase 2 now as far as I understand it: http://websvn.kde.org/branches/extragear/kde3/network/knetworkmanager/src/knetworkmanager-encryption.cpp?revision=682346&view=markup Has anyone tested this? Can we mark this bug as fixed?
Anja, swamp id for this update please. Note the version would bump.
This bug can be marked as fixed, current knetworkmanager SVN has a Phase2 field providing PAP,MSCHAP(v2) and GTC as an option.