Re: [PATCH] LEAP support in NetworkManager
- From: Jason Martens <me jasonmartens com>
- To: Thiago Bauermann <thiago bauermann gmail com>
- Cc: networkmanager-list gnome org
- Subject: Re: [PATCH] LEAP support in NetworkManager
- Date: Fri, 13 Oct 2006 13:27:39 -0500
Thiago Bauermann wrote:
2006/9/8, Thiago Bauermann <thiago bauermann gmail com 
<mailto:thiago bauermann gmail com>>:
    2006/9/8, Jason Martens <me jasonmartens com
    <mailto:me jasonmartens com>>:
        Jason Martens wrote:
        > Yes, I was still able to connect after removing the
        "auth_alg=OPEN LEAP"
        > line.
        >
        Have these changes made it into CVS yet? If so, I'll
        re-compile and try
        them out. :)
    Sorry pal. Still didn't get around to do it, but I believe I will
    in the next few days...
Mmmm... was more than a few days. But here it is, finally.
This patch adds Pairwise and Group options to the LEAP configuration 
dialog, which should address your wpa supplicant configuration.
--
[]'s
Thiago Jung Bauermann 
Awesome!
  I checked out the most recent version of CVS, and patched the source 
with your changes, make, checkinstall -D, etc.  However, I can't connect 
with NM to our network still.  I choose "Connect to other network", then 
choose LEAP as the authentication method, Key management: WPA-EAP, 
Pairwise: TKIP, Group: TKIP and enter my username and password.  For 
good measure, I tested again with my wpa_supplicant config, and that is 
working.  Below is the syslog output from N-M when I'm trying to 
connect.  Thoughts?
Thanks,
Jason Martens
Oct 13 13:16:14 mouse NetworkManager: <debug> [1160763374.086500] 
nm_device_802_11_wireless_get_activation_ap(): Forcing AP 'APNAME'
Oct 13 13:16:14 mouse NetworkManager: <info>  User Switch: 
/org/freedesktop/NetworkManager/Devices/eth2_5f_rename / APNAME
Oct 13 13:16:14 mouse NetworkManager: <info>  Deactivating device 
eth2_rename.
Oct 13 13:16:14 mouse dhcdbd: message_handler: message handler not found 
under /com/redhat/dhcp/eth2_rename for sub-path eth2_rename.dbus.get.reason
Oct 13 13:16:14 mouse NetworkManager: <info>  Device eth2_rename 
activation scheduled...
Oct 13 13:16:14 mouse NetworkManager: <info>  Activation (eth2_rename) 
started...
Oct 13 13:16:14 mouse NetworkManager: <info>  Activation (eth2_rename) 
Stage 1 of 5 (Device Prepare) scheduled...
Oct 13 13:16:14 mouse NetworkManager: <info>  Activation (eth2_rename) 
Stage 1 of 5 (Device Prepare) started...
Oct 13 13:16:14 mouse NetworkManager: <info>  Activation (eth2_rename) 
Stage 2 of 5 (Device Configure) scheduled...
Oct 13 13:16:14 mouse NetworkManager: <info>  Activation (eth2_rename) 
Stage 1 of 5 (Device Prepare) complete.
Oct 13 13:16:14 mouse NetworkManager: <info>  Activation (eth2_rename) 
Stage 2 of 5 (Device Configure) starting...
Oct 13 13:16:14 mouse NetworkManager: <info>  Activation 
(eth2_rename/wireless): access point 'APNAME' is encrypted, and a key 
exists.  No new key needed.
Oct 13 13:16:14 mouse kernel: ADDRCONF(NETDEV_UP): eth2_rename: link is 
not ready
Oct 13 13:16:14 mouse NetworkManager: <info>  Old device 'eth2_rename' 
activating, won't change.
Oct 13 13:16:14 mouse NetworkManager: <info>  SUP: sending command 
'INTERFACE_ADD eth2_rename^I^Iwext^I/var/run/wpa_supplicant^I'
Oct 13 13:16:14 mouse NetworkManager: <info>  SUP: response was 'OK'
Oct 13 13:16:14 mouse NetworkManager: <info>  SUP: sending command 
'AP_SCAN 2'
Oct 13 13:16:14 mouse NetworkManager: <info>  SUP: response was 'OK'
Oct 13 13:16:14 mouse NetworkManager: <info>  SUP: sending command 
'ADD_NETWORK'
Oct 13 13:16:14 mouse NetworkManager: <info>  SUP: response was '0'
Oct 13 13:16:14 mouse NetworkManager: <info>  SUP: sending command 
'SET_NETWORK 0 ssid some numbers'
Oct 13 13:16:14 mouse NetworkManager: <info>  SUP: response was 'OK'
Oct 13 13:16:14 mouse NetworkManager: <info>  SUP: sending command 
'SET_NETWORK 0 scan_ssid 1'
Oct 13 13:16:14 mouse NetworkManager: <info>  SUP: response was 'OK'
Oct 13 13:16:14 mouse NetworkManager: <info>  SUP: sending command 
'SET_NETWORK 0 key_mgmt NONE'
Oct 13 13:16:14 mouse NetworkManager: <info>  SUP: response was 'OK'
Oct 13 13:16:14 mouse NetworkManager: <info>  SUP: sending command 
'ENABLE_NETWORK 0'
Oct 13 13:16:14 mouse NetworkManager: <info>  SUP: response was 'OK'
Oct 13 13:16:14 mouse NetworkManager: <info>  Activation (eth2_rename) 
Stage 2 of 5 (Device Configure) complete.
Oct 13 13:16:14 mouse NetworkManager: <info>  Old device 'eth2_rename' 
activating, won't change.
Oct 13 13:16:34 mouse last message repeated 53 times
Oct 13 13:16:34 mouse NetworkManager: <info>  Activation 
(eth2_rename/wireless): association took too long (>20s), failing 
activation.
Oct 13 13:16:34 mouse NetworkManager: <info>  Activation (eth2_rename) 
failure scheduled...
Oct 13 13:16:34 mouse NetworkManager: <info>  Activation (eth2_rename) 
failed for access point (APNAME)
Oct 13 13:16:34 mouse NetworkManager: <info>  Activation (eth2_rename) 
failed.
Oct 13 13:16:34 mouse NetworkManager: <info>  Deactivating device 
eth2_rename.
Oct 13 13:16:34 mouse kernel: ADDRCONF(NETDEV_CHANGE): eth2_rename: link 
becomes ready
[
Date Prev][
Date Next]   [
Thread Prev][
Thread Next]   
[
Thread Index]
[
Date Index]
[
Author Index]