Re: PEAP with GTC in NetworkManager-0.7.0-0.12.svn4326.fc10.x86_64
- From: "Darren Albers" <dalbers gmail com>
- To: "David Orman" <ormandj corenode com>
- Cc: networkmanager-list gnome org
- Subject: Re: PEAP with GTC in NetworkManager-0.7.0-0.12.svn4326.fc10.x86_64
- Date: Fri, 19 Dec 2008 14:00:17 -0500
On Fri, Dec 19, 2008 at 12:24 PM, David Orman <ormandj corenode com> wrote:
> 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.
>
Ahh ok you are using RSA tokens so that means that the inner auth
likely has to be PAP or something equivalent since the RSA server
needs to receive the pin+passcode in plain-text. I ran into a
similar issue with trying to deploy PPTP with RSA tokens (FYI: Don't
do RSA+PPTP ;-) ).
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]