Re: [PATCH] LEAP support in NetworkManager
- From: "Thiago Bauermann" <thiago bauermann gmail com>
- To: "Dan Williams" <dcbw redhat com>
- Cc: networkmanager-list gnome org
- Subject: Re: [PATCH] LEAP support in NetworkManager
- Date: Fri, 11 Aug 2006 01:32:36 -0300
2006/7/13, Dan Williams <dcbw redhat com>:
Sorry to take so long to answer. You know... work, life, etc.
Also, I was trying to figure out some difficulties I was having with NM and my network environment (more on this in another e-mail).
> 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!).
Thanks! Looks really good, committed to HEAD with a few cleanups (2
unused variables, on missing return in a function with a return value
expected).
Great!
Could you provide the output of an 'iwlist <xxx> scan' command for an
access point that supports LEAP? Obviously change the BSSID and SSID
for your privacy, but I'm curious how they present themselves.
ath0 Scan completed :
Cell 03 - Address: 00:11:22:33:44:55
ESSID:"aaaaa"
Mode:Master
Frequency:2.412 GHz (Channel 1)
Quality=32/94 Signal level=-63 dBm Noise level=-95 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 6 Mb/s; 9 Mb/s
11 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Extra:bcn_int=100
Extra:wme_ie=something
SSID BSSID CHAN RATE S:N INT CAPS
aaaaa 00:11:22:33:44:55 1 54M 33:0 100 EPS WME
Also, do they send out an WPA or RSN information elements in the scan?
Nope...
Do they advertise that they support encryption?
Yup
Dan
> One of the issues is that in the first time you connect to the LEAP
> network, you need to use the "Connect to other wireless network" menu
> option and specify the SSID by hand, because NM thinks the network is
> not encrypted and tries to connect to it without bringing up the
> username/password dialog. After the first time, NM will store the
> network
> settings, so it's possible to use the menu item corresponding to the
> LEAP network in nm-applet from that point on.
Ok, actually the above is not true, actually. The thing is that for some weird reason some days there is an ad hoc, non encrypted AP with the same SSID of the corporate network I'm trying to connect to. I don't know if it's the IT department playing games or just some fellow co-worker trying to setup his own network in the office. Go figure. :-)
The fact is that AP confuses NM and then it tries to connect to it instead of the right master AP.
--
[]'s
Thiago Jung Bauermann
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]