Added Leap Support plus fixes

Bug #122059 reported by Lorenco Trichardt
12
Affects Status Importance Assigned to Milestone
network-manager (Ubuntu)
Invalid
Undecided
Alexander Sack
Declined for Gutsy by Brian Murray

Bug Description

Binary package hint: network-manager

+network-manager (0.6.4-6ubuntu7lud2) feisty; urgency=low
+
+ * Fixing postinst of network-manager package
+
+ -- Aloisio Almeida Jr Mon, 14 May 2007 13:43:26 -0300
+
+network-manager (0.6.4-6ubuntu7lud1) feisty; urgency=low
+
+ * Added LEAP support (ported from 0.6.3 LUD version)
+ * Added madwifi signal strenght report fix (ported from 0.6.3 LUD version)
+ * Added interface improvement
+ * Added patch to fix excessive reconnection
+
+ -- Aloisio Almeida Jr Sat, 05 May 2007 17:55:55 -0300
+

Revision history for this message
Lorenco Trichardt (trichalo) wrote :
Revision history for this message
Alexander Sack (asac) wrote :

Thanks for the patch.

Can you please attach a debdiff so I can easily review your specific changes?

and maybe give a brief comment for each single change as well.

Thanks for your contribution,

 - Alexander

Changed in network-manager:
assignee: nobody → asac
status: New → Incomplete
Revision history for this message
Lorenco Trichardt (trichalo) wrote : Re: [Bug 122059] Re: Added Leap Support plus fixes

The patch was written by my IBM colleague : Aloisio De Almeida in
Brazil.

I can see all the referals made in the diff file by him, (Forgot to
mention that in the last post as I as in a bit of a hurry. )
Does this help ?

On Wed, 2007-06-27 at 11:18 +0000, Alexander Sack wrote:

> Thanks for the patch.
>
> Can you please attach a debdiff so I can easily review your specific
> changes?
>
> and maybe give a brief comment for each single change as well.
>
> Thanks for your contribution,
>
> - Alexander
>
>
> ** Changed in: network-manager (Ubuntu)
> Assignee: (unassigned) => Alexander Sack
> Status: New => Incomplete
>

Groetnis ...
Lorenco Trichardt
<email address hidden>

---------------------------------------------
Written Today, 27 Jun 2007 at 13:40
---------------------------------------------

Revision history for this message
Alexander Sack (asac) wrote :

On Wed, Jun 27, 2007 at 11:44:54AM -0000, Lorenco Trichardt wrote:
> The patch was written by my IBM colleague : Aloisio De Almeida in
> Brazil.
>
> I can see all the referals made in the diff file by him, (Forgot to
> mention that in the last post as I as in a bit of a hurry. )
> Does this help ?

It would really help a lot if you or aloisio could just submit your
changes (vs. the whole diff.gz).

Let me know if you can do (please) ... otherwise, I can try to fiddle
those out and let you review if I catched everything (not preferred of
course).

Thanks,

 - Alexander

Revision history for this message
Alexander Sack (asac) wrote :

ok, here the diff against latest feisty. Anyone volunteers to port this to gutsy?

Revision history for this message
Mark Shuttleworth (sabdfl) wrote :

NM is a fairly key component for Gutsy, so +1 from me to get this patch integrated and tested.

Revision history for this message
Luxor (ranju-mathew) wrote :

I am running Gutsy with atheros wireless and following packages:

network-manager 0.6.5-0ubuntu12
network-manager-gnome 0.6.5-0ubuntu9
network-manager-openvpn 0.3.2svn2342-1ubuntu2
network-manager-pptp 0.6.5+svnhead2574-0ubuntu1
network-manager-vpnc 0.6.4svn2422-0ubuntu3

and I am unable to connect to a leap network using nm-applet. The wireless network does not appear automatically, so I have to manually choose 'connect to other network', set essid, choose leap, and put in the authentication information, and key management (WPA-EAP in my case), and click ok. Nm-applet just displays the rotating busy icon, and never connects.

I have wpasupplicant 0.6.0-3 installed, and can connect to the leap network using the following config file:
#/etc/wpa_supplicant/wpa_supplicant.conf
network={
        scan_ssid=1
        ssid="MYNETWORK"
        key_mgmt=WPA-EAP
        eap=LEAP
        identity="MYIDENTITY"
        password="MYPASSWORD"
}

command: wpa_supplicant -D madwifi -c /etc/wpa_supplicant/wpa_supplicant.conf -i ath0
I then run dhclient ath0, and everything works fine.

Revision history for this message
Alexander Sack (asac) wrote :

please attach your /var/log/syslog and daemon.log and don't forget to include the line where network-manager about the used driver ;).

Revision history for this message
Lorenco Trichardt (trichalo) wrote :

Here is both logs as requested....

Revision history for this message
Lorenco Trichardt (trichalo) wrote :
Revision history for this message
Luxor (ranju-mathew) wrote :
Download full text (15.3 KiB)

Alexander, here is my follow up to the first report:
When I first boot up and log into my account, nm-applet attempts to connect, but seems to not have the appropriate keys (according to syslog), so I choose 'Connect to Other Wireless Network...' and enter the information for leap, and see the attempts at connect, but ultimately, it fails.

syslog:
Oct 3 17:15:31 tardis NetworkManager: <info> Activation (ath0) Stage 1 of 5 (Device Prepare) complete.
Oct 3 17:15:31 tardis NetworkManager: <info> Activation (ath0) Stage 2 of 5 (Device Configure) starting...
Oct 3 17:15:31 tardis NetworkManager: <info> Activation (ath0/wireless): access point 'LEAP_SSID' is encrypted, but NO valid key exists. New key needed.
Oct 3 17:15:31 tardis NetworkManager: <info> Activation (ath0) New wireless user key requested for network 'LEAP_SSID'.
Oct 3 17:15:31 tardis NetworkManager: <info> Activation (ath0) Stage 2 of 5 (Device Configure) complete.
Oct 3 17:15:31 tardis NetworkManager: <info> Activation (ath0) New wireless user key for network 'LEAP_SSID' received.
Oct 3 17:15:31 tardis NetworkManager: <info> Activation (ath0) Stage 1 of 5 (Device Prepare) scheduled...
Oct 3 17:15:31 tardis NetworkManager: <info> Activation (ath0) Stage 1 of 5 (Device Prepare) started...
Oct 3 17:15:31 tardis NetworkManager: <info> Activation (ath0) Stage 2 of 5 (Device Configure) scheduled...
Oct 3 17:15:31 tardis NetworkManager: <info> Activation (ath0) Stage 1 of 5 (Device Prepare) complete.
Oct 3 17:15:31 tardis NetworkManager: <info> Activation (ath0) Stage 2 of 5 (Device Configure) starting...
Oct 3 17:15:31 tardis NetworkManager: <info> Activation (ath0/wireless): access point 'LEAP_SSID' is encrypted, but NO valid key exists. New key needed.
Oct 3 17:15:31 tardis NetworkManager: <info> Activation (ath0) New wireless user key requested for network 'LEAP_SSID'.
Oct 3 17:15:31 tardis NetworkManager: <info> Activation (ath0) Stage 2 of 5 (Device Configure) complete.
Oct 3 17:17:01 tardis /USR/SBIN/CRON[6359]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
Oct 3 17:17:39 tardis NetworkManager: <debug> [1191449859.266105] nm_device_802_11_wireless_get_activation_ap(): Forcing AP 'LEAP_SSID'
Oct 3 17:17:39 tardis NetworkManager: <info> User Switch: /org/freedesktop/NetworkManager/Devices/ath0 / IBM
Oct 3 17:17:39 tardis NetworkManager: <info> Deactivating device ath0.
Oct 3 17:17:39 tardis NetworkManager: <info> Activation (ath0): cancelling...
Oct 3 17:17:39 tardis NetworkManager: <info> Activation (ath0) cancellation handler scheduled...
Oct 3 17:17:39 tardis NetworkManager: <info> Activation (ath0): waiting for device to cancel activation.
Oct 3 17:17:39 tardis NetworkManager: <info> Activation (ath0) cancellation handled.
Oct 3 17:17:39 tardis NetworkManager: <info> Activation (ath0): cancelled.
Oct 3 17:17:39 tardis avahi-daemon[5775]: Withdrawing address record for fe80::216:cfff:fe26:42a2 on ath0.
Oct 3 17:17:39 tardis dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/ath0 for sub-path ath0.dbus.get.reason
Oct 3 17:17:39 tardis NetworkManager: <info> Device ath0 activation scheduled...
Oc...

Revision history for this message
Luxor (ranju-mathew) wrote :

I've found that this bug is related to https://bugs.launchpad.net/bugs/41134. /usr/bin/wpa_supplicant is not listed in the process list unless you re-login to a network by using the 'connect to other wireless network' option in nm-applet. When I do login, wpa_supplicant -g /var/run/wpa_supplicant-global<#> is called, and I can see some activity going to the madwifi interface using iwenvent. I have gotten it to connect, but when a new key needs to be generated for leap, it looses the connection. I am going to try the patch by Andrew Jorgensen, and will let you know what the results are.

Revision history for this message
Luxor (ranju-mathew) wrote :

Applied Andrew's fix. The password is being held in the keyring... (was doing so even before this fix), but I don't think the authentication information is being retrieved from the keyring to pass to wpa_supplicant by nm-applet. I don't see wpa in the process list until I use the 'connect to other wireless network'. Even after wpa runs, I am still unable to connect to the LEAP network. Is there some way to see the activity on the /var/run/wpa_supplicant-global socket so that we can see what is being passed to wpa_supplicant?

Revision history for this message
Luxor (ranju-mathew) wrote :

syslog.luxor is the log of the failures.
syslog.luxor4 is the log of the successful connection.

Please let me know if you need anything further. Also, how can I view the messages between nm and wpa_supplicant?
Thanks

Revision history for this message
Luxor (ranju-mathew) wrote :
Revision history for this message
Luxor (ranju-mathew) wrote :

Executing sudo /etc/dbus-1/event.d/25NetworkManager restart and trying 'Connect to Other Wireless Network' works.
However, it does not re-associate if I loose the connection, or move within the building to another location... which should prompt it to connect to the closest/strongest wireless AP.

Revision history for this message
Luxor (ranju-mathew) wrote :

network-manager 0.6.5-0ubuntu16
network-manager-gnome 0.6.5-0ubuntu10

Changed in network-manager:
status: Incomplete → Confirmed
Revision history for this message
Martin Mai (mrkanister-deactivatedaccount-deactivatedaccount) wrote :

Any news about this? Does network-manager 0.7 include leap support? Thanks.

Revision history for this message
Lorenco Trichardt (trichalo) wrote :

Yes, it works....
I was implemented a while back :)

Groetnis ...
Lorenco Trichardt
<email address hidden>

---------------------------------------------
Written Today, 15 Jan 2009 at 05:45
---------------------------------------------

-----Original Message-----
From: Martin Mai <email address hidden>
Reply-to: Bug 122059 <email address hidden>
To: <email address hidden>
Subject: [Bug 122059] Re: Added Leap Support plus fixes
Date: Wed, 14 Jan 2009 19:23:26 -0000

Any news about this? Does network-manager 0.7 include leap support?
Thanks.

Revision history for this message
Martin Mai (mrkanister-deactivatedaccount-deactivatedaccount) wrote :

Thanks Lorenco. So I am closing this bug due to your comemnt this being fixed.

Changed in network-manager:
status: Confirmed → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.