Re: Hi, NM and hidden ESSIDs

Hello Dan,
thanks for the response. I think i might have tracked down a bug in NM...but i'm not sure. When i go to gconf-editor and then drill down to where the AP information is saved at system -> networking -> wireless -> networks

I found that the last digit of the APs MAC address was off by one digit. It was saved at 83 when it really is 82 according to my linksys router  status page.  After fixing this, NM still doesn't connect automatically to my home network. I must use the connect to other wireless network option and it will again connect successfully but save the BSSID with the one digit off.  Also, gconf editor is saying that the keys don't have a schema so i'm not sure if that has to do with anything. My home router uses WPA2 personal.


On 4/15/06, Dan Williams <dcbw redhat com> wrote:
On Fri, 2006-04-14 at 08:53 -0400, Bruno Marc-AurXle wrote:
> Hello,
> I use NetworkManager with my IPW2200 and it works like a charm! The only
> thing I was wondering is if there was a way for NM to remember a hidden
> ESSID. For a non-encrypted network, it wouldn't be a problem, but for a WEP
> encrypted network, is causes me a problem: always rewrite the WEP key.
> Is there a possibility of doing this witht the current implementation or is
> there a way to add this feature (remembering hidden ESSIDs) without
> reprogramming a whole buch of stuff?

NM should be remembering hidden ESSIDs once you've successfully
connected to a specific AP/BSSID at least once.  When NM sees that BSSID
again, it looks up the ESSID for that BSSID and then tries to connect.
It may be broken, but if an 'iwlist eth1 scan' shows the BSSID of your
access point, then NM should be doing the right thing.

For example:

      Cell 08 - Address: 00:14:BF:8C:90:28  <--- BSSID
                Protocol:IEEE 802.11bg
                Encryption key:off
                Bit Rates:54 Mb/s
                Extra: Rates (Mb/s): 1 2 5.5 6 9 11 12 18 24 36 48 54
                Quality:20  Signal level:0  Noise level:0

It will probably look something like this from 'iwlist'.  If your AP
shows up, there's likely a bug in NM.


NetworkManager-list mailing list
NetworkManager-list gnome org

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]