Darren, Yes - I tried PEAPv1 using MSCHAPv2 first, and MD5 next as the inner auth methods. Neither worked. I think I still have some logs from this:
Dec 11 17:15:36 localhost NetworkManager: <info> Activation (wlan0) starting connection 'Auto SSIDWASHERE' Dec 11 17:15:36 localhost NetworkManager: <info> (wlan0): device state change: 3 -> 4 Dec 11 17:15:36 localhost NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled... Dec 11 17:15:36 localhost NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started... Dec 11 17:15:36 localhost NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled... Dec 11 17:15:36 localhost NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete. Dec 11 17:15:36 localhost NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting... Dec 11 17:15:36 localhost NetworkManager: <info> (wlan0): device state change: 4 -> 5 Dec 11 17:15:36 localhost NetworkManager: <info> Activation (wlan0/wireless): access point 'Auto SSIDWASHERE' has security, but secrets are required. Dec 11 17:15:36 localhost NetworkManager: <info> (wlan0): device state change: 5 -> 6 Dec 11 17:15:36 localhost NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete. Dec 11 17:15:36 localhost NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled... Dec 11 17:15:36 localhost NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started... Dec 11 17:15:36 localhost NetworkManager: <info> (wlan0): device state change: 6 -> 4 Dec 11 17:15:36 localhost NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled... Dec 11 17:15:36 localhost NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete. Dec 11 17:15:36 localhost NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting... Dec 11 17:15:36 localhost NetworkManager: <info> (wlan0): device state change: 4 -> 5 Dec 11 17:15:36 localhost NetworkManager: <info> Activation (wlan0/wireless): connection 'Auto SSIDWASHERE' has security, and secrets exist. No new secrets needed. Dec 11 17:15:36 localhost NetworkManager: <info> Config: added 'ssid' value 'SSIDWASHERE' Dec 11 17:15:36 localhost NetworkManager: <info> Config: added 'scan_ssid' value '1' Dec 11 17:15:36 localhost NetworkManager: <info> Config: added 'key_mgmt' value 'WPA-EAP' Dec 11 17:15:36 localhost NetworkManager: <info> Config: added 'password' value '<omitted>' Dec 11 17:15:36 localhost NetworkManager: <info> Config: added 'eap' value 'PEAP' Dec 11 17:15:36 localhost NetworkManager: <info> Config: added 'fragment_size' value '1300' Dec 11 17:15:36 localhost NetworkManager: <info> Config: added 'phase1' value 'peapver=1' Dec 11 17:15:36 localhost NetworkManager: <info> Config: added 'phase2' value 'auth=MSCHAPV2' Dec 11 17:15:36 localhost NetworkManager: <info> Config: added 'identity' value 'MYUSERNAMEHERE' Dec 11 17:15:36 localhost NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete. Dec 11 17:15:36 localhost NetworkManager: <info> Config: set interface ap_scan to 1 Dec 11 17:15:36 localhost NetworkManager: <info> (wlan0): supplicant connection state: disconnected -> scanning Dec 11 17:15:50 localhost NetworkManager: <info> (wlan0): supplicant connection state: scanning -> disconnected Dec 11 17:15:51 localhost NetworkManager: <info> (wlan0): supplicant connection state: disconnected -> associated Dec 11 17:15:51 localhost NetworkManager: <info> (wlan0): supplicant connection state: associated -> disconnected Dec 11 17:16:01 localhost NetworkManager: <info> Activation (wlan0/wireless): association took too long. Dec 11 17:16:01 localhost NetworkManager: <info> (wlan0): device state change: 5 -> 6 Dec 11 17:16:01 localhost NetworkManager: <info> Activation (wlan0/wireless): asking for new secrets Dec 11 17:16:06 localhost NetworkManager: <info> (wlan0): supplicant connection state: disconnected -> associated Dec 11 17:16:06 localhost NetworkManager: <info> (wlan0): supplicant connection state: associated -> disconnected Dec 11 17:16:11 localhost NetworkManager: <info> (wlan0): supplicant connection state: disconnected -> scanning Dec 11 17:16:15 localhost NetworkManager: <info> (wlan0): supplicant connection state: scanning -> associating Dec 11 17:16:15 localhost NetworkManager: <info> (wlan0): supplicant connection state: associating -> disconnected Dec 11 17:16:15 localhost NetworkManager: <info> (wlan0): supplicant connection state: disconnected -> associated Dec 11 17:16:21 localhost NetworkManager: <info> wlan0: link timed out. Some more: Dec 11 23:43:35 localhost NetworkManager: <info> Activation (wlan0) starting connection 'Auto SSIDWASHERE' Dec 11 23:43:35 localhost NetworkManager: <info> (wlan0): device state change: 3 -> 4 Dec 11 23:43:35 localhost NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled... Dec 11 23:43:35 localhost NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started... Dec 11 23:43:35 localhost NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled... Dec 11 23:43:35 localhost NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete. Dec 11 23:43:35 localhost NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting... Dec 11 23:43:35 localhost NetworkManager: <info> (wlan0): device state change: 4 -> 5 Dec 11 23:43:35 localhost NetworkManager: <info> Activation (wlan0/wireless): access point 'Auto SSIDWASHERE' has security, but secrets are required. Dec 11 23:43:35 localhost NetworkManager: <info> (wlan0): device state change: 5 -> 6 Dec 11 23:43:35 localhost NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete. Dec 11 23:43:35 localhost NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled... Dec 11 23:43:35 localhost NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started... Dec 11 23:43:35 localhost NetworkManager: <info> (wlan0): device state change: 6 -> 4 Dec 11 23:43:35 localhost NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled... Dec 11 23:43:35 localhost NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete. Dec 11 23:43:35 localhost NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting... Dec 11 23:43:35 localhost NetworkManager: <info> (wlan0): device state change: 4 -> 5 Dec 11 23:43:35 localhost NetworkManager: <info> Activation (wlan0/wireless): connection 'Auto SSIDWASHERE' has security, and secrets exist. No new secrets needed. Dec 11 23:43:35 localhost NetworkManager: <info> Config: added 'ssid' value 'SSIDWASHERE' Dec 11 23:43:35 localhost NetworkManager: <info> Config: added 'scan_ssid' value '1' Dec 11 23:43:35 localhost NetworkManager: <info> Config: added 'key_mgmt' value 'WPA-EAP' Dec 11 23:43:35 localhost NetworkManager: <info> Config: added 'password' value '<omitted>' Dec 11 23:43:35 localhost NetworkManager: <info> Config: added 'eap' value 'PEAP' Dec 11 23:43:35 localhost NetworkManager: <info> Config: added 'fragment_size' value '1300' Dec 11 23:43:35 localhost NetworkManager: <info> Config: added 'phase1' value 'peapver=1' Dec 11 23:43:35 localhost NetworkManager: <info> Config: added 'phase2' value 'auth=MSCHAPV2' Dec 11 23:43:35 localhost NetworkManager: <info> Config: added 'identity' value 'USERNAMEWASHERE' Dec 11 23:43:35 localhost NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete. Dec 11 23:43:35 localhost NetworkManager: <info> Config: set interface ap_scan to 1 Dec 11 23:43:35 localhost NetworkManager: <info> (wlan0): supplicant connection state: disconnected -> scanning Dec 11 23:43:39 localhost NetworkManager: <info> (wlan0): supplicant connection state: scanning -> associating Dec 11 23:43:39 localhost NetworkManager: <info> (wlan0): supplicant connection state: associating -> disconnected Dec 11 23:43:39 localhost NetworkManager: <info> (wlan0): supplicant connection state: disconnected -> associated Dec 11 23:43:54 localhost NetworkManager: <info> wlan0: link timed out. Dec 11 23:44:00 localhost NetworkManager: <info> Activation (wlan0/wireless): association took too long. Dec 11 23:44:00 localhost NetworkManager: <info> (wlan0): device state change: 5 -> 6 Dec 11 23:44:00 localhost NetworkManager: <info> Activation (wlan0/wireless): asking for new secrets Dec 11 23:44:00 localhost NetworkManager: <info> (wlan0): supplicant connection state: associated -> disconnected Dec 11 23:44:15 localhost NetworkManager: <info> wlan0: link timed out. Dec 11 23:44:33 localhost NetworkManager: <WARN> get_secrets_cb(): Couldn't get connection secrets: applet-device-wifi.c.1542 (get_secrets_dialog_response_cb): canceled. Dec 11 23:44:33 localhost NetworkManager: <info> (wlan0): device state change: 6 -> 9 Dec 11 23:44:33 localhost NetworkManager: <info> Activation (wlan0) failed for access point (SSIDWASHERE) Dec 11 23:44:33 localhost NetworkManager: <info> Marking connection 'Auto SSIDWASHERE' invalid. Dec 11 23:44:33 localhost NetworkManager: <info> Activation (wlan0) failed. With MD5: Dec 11 23:51:08 localhost NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled... Dec 11 23:51:08 localhost NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started... Dec 11 23:51:08 localhost NetworkManager: <info> (wlan0): device state change: 6 -> 4 Dec 11 23:51:08 localhost NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled... Dec 11 23:51:08 localhost NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete. Dec 11 23:51:08 localhost NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting... Dec 11 23:51:08 localhost NetworkManager: <info> (wlan0): device state change: 4 -> 5 Dec 11 23:51:08 localhost NetworkManager: <info> Activation (wlan0/wireless): connection 'Auto SSIDWASHERE' has security, and secrets exist. No new secrets needed. Dec 11 23:51:08 localhost NetworkManager: <info> Config: added 'ssid' value 'SSIDWASHERE' Dec 11 23:51:08 localhost NetworkManager: <info> Config: added 'scan_ssid' value '1' Dec 11 23:51:08 localhost NetworkManager: <info> Config: added 'key_mgmt' value 'WPA-EAP' Dec 11 23:51:08 localhost NetworkManager: <info> Config: added 'password' value '<omitted>' Dec 11 23:51:08 localhost NetworkManager: <info> Config: added 'eap' value 'PEAP' Dec 11 23:51:08 localhost NetworkManager: <info> Config: added 'fragment_size' value '1300' Dec 11 23:51:08 localhost NetworkManager: <info> Config: added 'phase1' value 'peapver=1' Dec 11 23:51:08 localhost NetworkManager: <info> Config: added 'phase2' value 'auth=MD5' Dec 11 23:51:08 localhost NetworkManager: <info> Config: added 'identity' value 'USERNAMEWASHERE' Dec 11 23:51:08 localhost NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete. Dec 11 23:51:08 localhost NetworkManager: <info> Config: set interface ap_scan to 1 Dec 11 23:51:08 localhost NetworkManager: <info> (wlan0): supplicant connection state: disconnected -> scanning Dec 11 23:51:12 localhost NetworkManager: <info> (wlan0): supplicant connection state: scanning -> associating Dec 11 23:51:12 localhost NetworkManager: <info> (wlan0): supplicant connection state: associating -> disconnected Dec 11 23:51:12 localhost NetworkManager: <info> (wlan0): supplicant connection state: disconnected -> associated Dec 11 23:51:27 localhost NetworkManager: <info> wlan0: link timed out. Dec 11 23:51:33 localhost NetworkManager: <info> Activation (wlan0/wireless): association took too long. Dec 11 23:51:33 localhost NetworkManager: <info> (wlan0): device state change: 5 -> 6 Dec 11 23:51:33 localhost NetworkManager: <info> Activation (wlan0/wireless): asking for new secrets Dec 11 23:51:33 localhost NetworkManager: <info> (wlan0): supplicant connection state: associated -> disconnected Dec 11 23:51:38 localhost NetworkManager: <info> (wlan0): supplicant connection state: disconnected -> scanning Dec 11 23:51:41 localhost NetworkManager: <info> (wlan0): supplicant connection state: scanning -> disconnected Dec 11 23:51:41 localhost NetworkManager: <info> (wlan0): supplicant connection state: disconnected -> associated Dec 11 23:51:41 localhost NetworkManager: <info> (wlan0): supplicant connection state: associated -> disconnected Dec 11 23:51:43 localhost NetworkManager: <info> (wlan0): supplicant connection state: disconnected -> associated Dec 11 23:51:43 localhost NetworkManager: <info> (wlan0): supplicant connection state: associated -> disconnected >From the wpa_supplicant.log: Trying to associate with MACADDIEWASHERE (SSID='SSIDWASHERE' freq=24xx MHz) CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys Associated with MACADDIEWASHERE CTRL-EVENT-EAP-STARTED EAP authentication started CTRL-EVENT-EAP-METHOD EAP vendor 0 method 25 (PEAP) selected EAP-PEAP: Failed to select forced PEAP version 1 CTRL-EVENT-SCAN-RESULTS CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys CTRL-EVENT-SCAN-RESULTS CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys *snip snip, lots more remove keys* [r...@ormandj-laptop log]# rpm -qa |grep wpa_supplicant wpa_supplicant-0.6.4-2.fc10.x86_64 [r...@ormandj-laptop log]# [r...@ormandj-laptop log]# rpm -qa |grep Network NetworkManager-gnome-0.7.0-0.12.svn4326.fc10.x86_64 NetworkManager-glib-0.7.0-0.12.svn4326.fc10.x86_64 NetworkManager-0.7.0-0.12.svn4326.fc10.x86_64 NetworkManager-vpnc-0.7.0-0.11.svn4326.fc10.x86_64 NetworkManager-openvpn-0.7.0-16.svn4326.fc10.x86_64 [r...@ormandj-laptop log]# Hope this helps! David On Fri, Dec 19, 2008 at 11:06 AM, Darren Albers <[email protected]> wrote: > On Fri, Dec 19, 2008 at 11:52 AM, David Orman <[email protected]> > wrote: > > Hi Dan, > > > > Here's some more information about PEAP-GTC. > > > > First, a little snippit from the freeradius project: > > http://wiki.freeradius.org/EAP#PEAPv1.2FEAP-GTC > > It references the RFC in which PEAP-GTC is defined as an inner > > authentication protocol: http://www.ietf.org/rfc/rfc3748.txt > > In the RFC, the relevant section is 5.6 > > > > In our environment, we utilize RSA tokens with a randomly generated keys, > so > > I think it is likely the method you are thinking of. You're correct in > your > > analysis, it would certainly be an always prompt/never save bit in the > > application. Running a search to gather more information to help out, all > I > > ran into were posts about people who had upgraded various distributions > and > > gotten NM 0.7.x (that had been running 0.6.x with working PEAP-GTC > support), > > so it does seem to be utilized somewhat frequently. wpa_supplicant > appears > > to still work correctly with PEAP-GTC for most people, as does NM 0.6.x, > so > > most people who are in the same boat as I am have been downgrading to the > > older version of NM or just using wpa_supplicant directly. > > > > I'm happy to assist however I can in this, but I will likely be limited > to > > providing myself as a lab rat for testing changes. Anybody is more than > > welcome to take me up on that offer. :) Let me know if there is any other > > information I can gather that would help out, and thank you for looking > into > > this! > > > > Cheers, > > David > > I have never seen PEAP-GTC in use before but the Cisco docs I have > /seem/ to use PEAPv1 and PEAP-GTC interchangeably. Have you tried > setting up your connection as PEAPv1? >
_______________________________________________ NetworkManager-list mailing list [email protected] http://mail.gnome.org/mailman/listinfo/networkmanager-list
