Re: Cannot connect to wpa/wpa2 network with hidden SSID

[Dan Williams <dcbw redhat com>]

On Thu, 2009-07-09 at 13:58 +0800, 代尔欣 wrote:
> Hi Dan, 
>       The attach is the wpa_supplicant.log when accessing hidden AP.
> Please help take a look. Thanks in advance. NM can't connect to the
> hidden AP(ssid:HIDE pass:12345678 key_mgmt:WPA-PSK).

This log doesn't look like you've asked NM to try and connect; I'd need
a log where you've tried the "Connect to hidden network..." option from
the menu.

The supplicant isnt' able to probe-scan to find your AP because it
doesn't have the information yet to be able to do so.  Once you've
successfully connected, NM will cache the AP's BSSID and recognize that
AP from the scan list and try to reconnect automatically.  But the first
time has to be manual, because otherwise there's no way to find the AP
since it's trying to hide.

Hiding isn't actually a useful method of increasing security, since the
AP's beacon and BSSID are always available in probe responses; so anyone
can actually get the SSID irregardless of whether the AP is broadcasting
that information in its beacon.

Dan


> 2009/7/8 Dan Williams <dcbw redhat com>
>         On Wed, 2009-07-08 at 21:20 +0800, 代尔欣 wrote:
>         > Yes! I also met the problem. When the AP config changed, it
>         can't be
>         > connected through the NM. I am not sure whether it is the
>         same problem
>         > I mentioned in pre mail.
>         
>         
>         NM sends a permissive config to the supplicant, and will allow
>         the
>         supplicant to connect with either WPA or WPA2.  What you
>         probably want
>         to do here to debug the supplicant is to add "-dddt" to the
>         end of teh
>         Exec= line
>         in /usr/share/dbus-1/system-services/fi.epitest.hostap.WPASupplicant.service, then 'sudo killall -TERM wpa_supplicant', and grab output from /var/log/wpa_supplicant.log so we can diagnose.
>         
>         Changing ap_scan isn't the right thing to do, it's a hack, and
>         if
>         ap_scan=2 works, that indicates you have driver (or
>         supplicant) bugs.
>         
>         Dan
>         
>         
>         > 2009/7/8 Trey Nolen <support internetpro net>
>         >
>         >         > 2009/2/27 Joshua C. <joshuacov googlemail com>
>         >         >         I cannot connect with the latest
>         Networkmanager to
>         >         any network
>         >         >         with
>         >         >         wpa/wpa2 that doesn't broadcast its name.
>         Once the
>         >         name is
>         >         >         revealed
>         >         >         there are no problems. This is on Fedora
>         11 and
>         >         there's a bug
>         >         >         about it
>         >         >         here:
>         >         https://bugzilla.redhat.com/show_bug.cgi?id=486877
>         >         >
>         >         >         Installed are:
>         >         >         NetworkManager-0.7.0.98-1.git20090225.fc11
>         >         >
>         NetworkManager-gnome-0.7.0.98-1.git20090225.fc11
>         >         >
>         NetworkManager-glib-0.7.0.98-1.git20090225.fc11
>         >         >         wpa_supplicant-0.6.7-4.fc11
>         >         >         wpa_supplicant-gui-0.6.7-4.fc11
>         >
>         >         >
>         >         >
>         >         >         i had this problem some months ago. Then
>         it was with
>         >         f9/f10
>         >         >         and it was
>         >         >         fixed later. but now it's back again.
>         >
>         >
>         >
>         >         I also had (have) a similar problem on Ubuntu 9.04.
>          However,
>         >         it also
>         >         happens when the SSID is not hidden.  It seems to
>         only happen
>         >         when the
>         >         AP will auto switch between WPA and WPA2.  If I
>         force the AP
>         >         to pick
>         >         one, it works OK. I'm not sure if this is rooted in
>         the same
>         >         issue.
>         >
>         >         I'm afraid I haven't done much research into it to
>         see if
>         >         there are any
>         >         previous bug reports. I just changed the setting on
>         the AP and
>         >         went on
>         >         with life...
>         >
>         >
>         >         Trey Nolen
>         >
>         >
>         >
>         >
>         
>         
>         > _______________________________________________
>         > NetworkManager-list mailing list
>         > NetworkManager-list gnome org
>         > http://mail.gnome.org/mailman/listinfo/networkmanager-list
>         
>         
>