Re: [PATCH] LEAP support in NetworkManager
2006/10/13, Jason Martens [EMAIL PROTECTED]: Alright, I tried it without the group and pairwise options, and it worksusing wpa_supplicant, so I re-installed my pre-Thiago patch NM, andtried to connect to the AP using the existing LEAP support, whichfailed.So, I have still yet to successfully connect to this AP using NM.Below is the (most recent) working wpa_supplicant config, and thesyslog of NM trying to connect to the same AP (without the extra LEAPoptions).Ok, so NM is timing out when trying to connect to the AP. When you connect using wpa_supplicant, does it take a long time to associate? Maybe NM is quitting too soon.What is the driver wpa_supplicant is using (wext, madwifi, etc.)? And does it use the eth2_rename interface? That is a strange name for an interface, maybe it has something to do with your problem, who knows... -- []'sThiago Jung Bauermann ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: [PATCH] LEAP support in NetworkManager
On Fri, 2006-10-13 at 01:04 -0300, Thiago Bauermann wrote: 2006/9/8, Thiago Bauermann [EMAIL PROTECTED]: 2006/9/8, Jason Martens [EMAIL PROTECTED]: 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. Looking over this again though, do we really need to add this option? By default, the LEAP stuff doesn't specify auth_alg, which means wpa_supplicant should be using OPEN LEAP as the auth_alg by default. The next question I have is whether or not Jason's setup works when he leaves out the 'group' and 'pairwise' options. If so, then we probably don't need the patch here to specify them (sorry Thiago, very great work so far, I just want to make sure we really need more UI options before we add them). Some APs seem to require exactly the configuration that they support, and also that if you are using a hidden SSID, you have to specify only the configuration options which the AP supports. Jason? Can you test removing the 'group' and 'pairwise' options from your wpa_supplicant config and see if that works as well? Thanks! Dan -- []'s Thiago Jung Bauermann ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: [PATCH] LEAP support in NetworkManager
Thiago Bauermann wrote: 2006/9/8, Thiago Bauermann [EMAIL PROTECTED] mailto:[EMAIL PROTECTED]: 2006/9/8, Jason Martens [EMAIL PROTECTED] mailto:[EMAIL PROTECTED]: 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 ___ NetworkManager-list mailing list NetworkManager-list@gnome.org
Re: [PATCH] LEAP support in NetworkManager
Jason Martens wrote: Thiago Bauermann wrote: 2006/8/11, Jason Martens [EMAIL PROTECTED] mailto:[EMAIL PROTECTED]: With this config file, I was able to associate with the access point, and I was then able to get an IP address. So, I think the answer to your question is yes, that's all I had to do. In the interest of avoiding generating a config with more options than necessary, can you see if you are still able to connect without the auth_alg=OPEN LEAP line in your wpa_supplicant config file? If that doesn't work, then try just with auth_alg=LEAP, please. -- []'s Thiago Jung Bauermann 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. :) Thanks, Jason Martens ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: [PATCH] LEAP support in NetworkManager
2006/9/8, Jason Martens [EMAIL PROTECTED]: 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 trythem out. :) Sorry pal. Still didn't get around to do it, but I believe I will in the next few days...-- []'sThiago Jung Bauermann ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: [PATCH] LEAP support in NetworkManager
2006/8/11, Jason Martens [EMAIL PROTECTED]: With this config file, I was able to associate with the access point, and I was then able to get an IP address. So, I think the answer to your question is yes, that's all I had to do.In the interest of avoiding generating a config with more options thannecessary, can you see if you are still able to connect without theauth_alg=OPEN LEAP line in your wpa_supplicant config file? If that doesn't work, then try just with auth_alg=LEAP, please.-- []'sThiago Jung Bauermann ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: [PATCH] LEAP support in NetworkManager
2006/8/9, Jason Martens [EMAIL PROTECTED]:
Dan Williams wrote: Hmm, I don't think so...does wpa_supplicant support that?Turns out that it does.Here's my wpa_supplicant conf file:network={ssid=essidscan_ssid=1
key_mgmt=WPA-EAPgroup=TKIPpairwise=TKIPauth_alg=OPEN LEAPeap=LEAPpriority=2proto=WPAidentity=usernamepassword=password
}If you want it, I can send the debugging output from wpa_supplicant whenI connect.No debug info necessary. Actually, the only real work the new LEAP support in NM does is writing a suitable configuration file for wpa_supplicant. I can add support for the above config options in the NM LEAP code. Is the above config the only thing you need to do to get going?
-- []'sThiago Jung Bauermann
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: [PATCH] LEAP support in NetworkManager
Dan Williams wrote:
On Wed, 2006-08-02 at 13:44 -0500, Jason Martens wrote:
Alright, I've finally succeeded in building n-m from CVS with leap
support. We use a (perhaps) strange wireless configuration here, where
the Cisco Access Points run two separate wireless networks off of one
access point. One is unencrypted, the other uses WPA-Enterprise, TKIP
and LEAP. I cannot connect to the WPA access point even with the LEAP
support. Does the current LEAP support allow for TKIP?
Hmm, I don't think so... does wpa_supplicant support that?
Dan
Turns out that it does. Here's my wpa_supplicant conf file:
network={
ssid=essid
scan_ssid=1
key_mgmt=WPA-EAP
group=TKIP
pairwise=TKIP
auth_alg=OPEN LEAP
eap=LEAP
priority=2
proto=WPA
identity=username
password=password
}
If you want it, I can send the debugging output from wpa_supplicant when
I connect.
Jason
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: [PATCH] LEAP support in NetworkManager
Dan Williams wrote: On Mon, 2006-07-24 at 15:53 -0500, Aaron Konstam wrote: On Thu, 2006-07-13 at 13:07 -0400, Dan Williams wrote: On Fri, 2006-07-07 at 20:32 -0300, Thiago Bauermann wrote: Hi folks, This is a patch which adds LEAP support to NetworkManager. It has two issues which I am aware of, but it's most definetly usable (and useful!). I am interested in the LEAP support but I am unclear where to find the NM that contains it. Is it one of the distributions of source code you can get from the NetworkManager home site? If so which is it? It's committed to CVS and is in CVS HEAD, but it's not in a release yet. If you can test from CVS that would be great. I just downloaded the most recent CVS to test leap, and I'm getting a compile error on Ubuntu Dapper: cc1: warnings being treated as errors interface_parser.c: In function 'add_data': interface_parser.c:56: warning: ISO C90 forbids mixed declarations and code Any thoughts? Thanks, Jason Martens ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: [PATCH] LEAP support in NetworkManager
Edit configure.in and remove -Werror so it does not treat warnings as errors. On 7/31/06, Jason Martens [EMAIL PROTECTED] wrote: Dan Williams wrote: On Mon, 2006-07-24 at 15:53 -0500, Aaron Konstam wrote: On Thu, 2006-07-13 at 13:07 -0400, Dan Williams wrote: On Fri, 2006-07-07 at 20:32 -0300, Thiago Bauermann wrote: Hi folks, This is a patch which adds LEAP support to NetworkManager. It has two issues which I am aware of, but it's most definetly usable (and useful!). I am interested in the LEAP support but I am unclear where to find the NM that contains it. Is it one of the distributions of source code you can get from the NetworkManager home site? If so which is it? It's committed to CVS and is in CVS HEAD, but it's not in a release yet. If you can test from CVS that would be great. I just downloaded the most recent CVS to test leap, and I'm getting a compile error on Ubuntu Dapper: cc1: warnings being treated as errors interface_parser.c: In function 'add_data': interface_parser.c:56: warning: ISO C90 forbids mixed declarations and code Any thoughts? Thanks, Jason Martens ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: [PATCH] LEAP support in NetworkManager
On Mon, 2006-07-24 at 15:53 -0500, Aaron Konstam wrote: On Thu, 2006-07-13 at 13:07 -0400, Dan Williams wrote: On Fri, 2006-07-07 at 20:32 -0300, Thiago Bauermann wrote: Hi folks, This is a patch which adds LEAP support to NetworkManager. It has two issues which I am aware of, but it's most definetly usable (and useful!). I am interested in the LEAP support but I am unclear where to find the NM that contains it. Is it one of the distributions of source code you can get from the NetworkManager home site? If so which is it? It's committed to CVS and is in CVS HEAD, but it's not in a release yet. If you can test from CVS that would be great. Dan ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: [PATCH] LEAP support in NetworkManager
On Thu, 2006-07-13 at 13:07 -0400, Dan Williams wrote: On Fri, 2006-07-07 at 20:32 -0300, Thiago Bauermann wrote: Hi folks, This is a patch which adds LEAP support to NetworkManager. It has two issues which I am aware of, but it's most definetly usable (and useful!). I am interested in the LEAP support but I am unclear where to find the NM that contains it. Is it one of the distributions of source code you can get from the NetworkManager home site? If so which is it? -- Aaron Konstam [EMAIL PROTECTED] ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
