Re: ifcfg-rh and wpa_supplicant

[Dan Williams <dcbw redhat com>]

On Sat, 2012-05-19 at 06:17 +0200, Oncaphillis wrote:
> On 05/19/2012 03:43 AM, Dan Williams wrote:
> > On Fri, 2012-05-18 at 23:39 +0200, Oncaphillis wrote:
> >> On 05/18/2012 11:23 PM, Dan Williams wrote:
> >>> On Thu, 2012-05-17 at 09:58 +0200, Oncaphillis wrote:
> >>>> Hi,
> >>>>
> >>>>     I'm using Fedora16 and I'm trying to set up NetworkManager to connect
> >>>> to a wlan on startup via /etc/sysconfig/network-scrip/ifcfg-wlan0 or
> >>>> /etc/sysconfig/network-scrip/ifcfg-<ESSID>.  It seems the settings in
> >>>> /etc/sysconfig/wpa_supplicant are ignored if wpa_supplicant is managed
> >>>> by the NetworkManager,but I don't see any option to pass the -D<driver>
> >>>> option to wpa_supplicant.
> >>>
> >>> Correct, the settings in /etc/sysconfig/wpa_supplicant can be harmful
> >>> when NetworkManager is used, because NetworkManager figures out whether
> >>> to use the wext, nl80211, or wired driver as appropriate.  What's the
> >>> reason you want to use a specific supplicant driver?
> >>>
> >>> Dan
> >>>
> >>
> >> Simply the observation that wpa_supplicant fails to associate when
> >> not using -Dwext
> >
> > What wifi kernel driver?
> <snip>
> 04:00.0 Network controller: Atheros Communications Inc. AR928X Wireless 
> Network Adapter (PC
>          Subsystem: Device 1a3b:1067
>          Flags: bus master, fast devsel, latency 0, IRQ 18
>          Memory at febf0000 (64-bit, non-prefetchable) [size=64K]
>          Capabilities: [40] Power Management version 2
>          Capabilities: [50] MSI: Enable- Count=1/1 Maskable- 64bit-
>          Capabilities: [60] Express Legacy Endpoint, MSI 00
>          Capabilities: [90] MSI-X: Enable- Count=1 Masked-
>          Capabilities: [100] Advanced Error Reporting
>          Capabilities: [140] Virtual Channel
>          Capabilities: [160] Device Serial Number 00-00-00-00-00-00-00-00
>          Kernel driver in use: ath9k
>          Kernel modules: ath9k

That device is driven by the ath9k driver, which is one of the
better-supported mac80211 chipsets, so it should certainly work with
nl80211.  If it's not working, then we need to get some supplicant and
kernel debugging information to see what's wrong in the driver.  What
kernel version do you have?

Dan