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