Re: Converting wpa_supplicat.conf to NetworkManager setup

On Thu, 2008-03-13 at 14:18 -0400, Matt Lavin wrote:
> I've got a wpa_supplicat.conf file that can connect to my wireless
> network, but I can't figure out how to make NetworkManager use the
> same settings.  My wpa_supplicat.conf file looks like this:
> # ap_scan=2
> network={
>     ssid="<my-ssid>"
>     proto=WPA2
>     key_mgmt=WPA-EAP
>     eap=TLS
>     identity="<my-id>"
> # scan_ssid=1
>     private_key="<my-key>"
>     private_key_passwd="<my-password>"
>     priority=1
> }
> I tried to setup a corresponding WPA2 Enterprise with the fields as
> you would expect, but when network manager connects it adds in the two
> commented lined above.  If I add those two lines to my
> wpa_supplicat.conf fie then I can't connect.  Does anybody know how to
> make NetworkManager use my wpa_supplicat.conf file above?

This means your wireless driver does not support scan capabilities, and
doesn't implement the WEXT specification correctly.  I'd ask your distro
vendor to apply the scan capability patch to their kernel (it's quite
small and low-impact and already in 2.6.24) and then you should be fine.

The problem is that NM cannot detect whether your driver has the ability
to use ap_scan=1 or whether it must fall back to ap_scan=2.  Drivers
that do not work with ap_scan=2 are _broken_ by definition, but this is
a workaround.


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