XO: Network Manager and hidden ESSID

[Ludek Smid]

Hello,

it seems that there are problems with hidden ESSID on encrypted networks 
(WEB and WPA/WPA2).

When I select "Connect to Hidden Wireless Network" and enter correct 
connection parameters I end with "Activation (eth0/wireless): 
association took too long" in /var/log/messages. Displayed dialog asking 
for new secrets does not contain WPA/WPA2. NM stores wireless network info.

However, when I cancel the dialog and click on (now visible) hidden 
ESSID, I get correct dialog asking for secrets and connection is 
successfully completed.

There is already a bug 
https://bugzilla.redhat.com/show_bug.cgi?id=448437 for an older version 
of NM.

Can anyone confirm that it's not an XO specific bug?

Thanks,

Ludek

[Ludek Smid]

Ludek Smid wrote:
>  it seems that there are problems with hidden ESSID on encrypted
> networks 
>  (WEB and WPA/WPA2). 
It seems that it was my fault -- I did select unsupported mesh
device 
which is listed first. User have to select second device (with identical 
name) to setup connection right.

Ludek

[Scott Robbins]

On Tue, Nov 11, 2008 at 10:30:58PM +0100, Ludek Smid wrote:
>  Ludek Smid wrote:
> > it seems that there are problems with hidden ESSID on encrypted 
> > networks (WEB and WPA/WPA2). 
It works fine for me.  On the other hand, I don't use NM, nor do I have
a device running at boot.  I have a wpa_supplicant.conf set up--hidden
networks require the line
scan_ssid=1

If you mean a problem with NM and that, well, there are advantages to
being a dinosaur. 


-- 
Scott Robbins
PGP keyID EB3467D6
( 1B48 077D 66F6 9DB0 FDC2 A409 FA54 EB34 67D6 )
gpg --keyserver pgp.mit.edu --recv-keys EB3467D6

Willow: So, how did it go? 
Xander: On a scale from one to ten? It sucked.