Re: NM does not work with iwl4965 device
- From: "John W. Linville" <linville tuxdriver com>
- To: Dan Williams <dcbw redhat com>
- Cc: Thomas M Steenholdt <tmus tmus dk>, networkmanager-list gnome org
- Subject: Re: NM does not work with iwl4965 device
- Date: Wed, 8 Aug 2007 10:53:12 -0400
On Wed, Aug 08, 2007 at 07:34:47AM -0400, Dan Williams wrote:
> 1 means wpa_supplicant scans around and tries to find the AP. But if
> the AP is "hidden", wpa_supplicant won't find it because wpa_supplicant
> doesn't know how to find hidden APs. NM works around that by caching
> the BSSID after a successful connection, and when it finds that BSSID in
> scan results, filling in the SSID.
>
> 2 means NM must fill out the config for the network completely, and
> wpa_supplicant just blows those settings to the card and waits for the
> association to succeed. This is most closely analogous to a lot of
> 'iwconfig' commands. Only in this mode can wpa_supplicant really
> connect to a hidden network, because NM would have given wpa_supplicant
> both SSID and BSSID.
>
> So it's understandable why wpa_supplicant doesn't set the SSID on the
> card when you give it AP_SCAN=1, because it can't _find_ that SSID in
> scan results precisely because the SSID isn't broadcasting it's SSID.
So, wpa_supplicant only requests a scan? It never sends any probes
itself? Forgive me if this is an ignorant question -- I haven't
peered much into these userland bits...
John
--
John W. Linville
linville tuxdriver com
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]