Incorrect signal levels reported using wpa_supplicant's driver_nl80211

Dan Williams dcbw
Mon Nov 9 22:27:48 PST 2009

On Mon, 2009-11-09 at 14:09 +0100, Marcel Holtmann wrote:
> Hi Johannes,
> > > > Soon.  We've got some patches for this, but we'll also need tons of
> > > > testing.  The WEXT stuff is pretty baked while nl80211 is still under
> > > > some flux.  But of course the only way we bake nl80211 is by switching
> > > > to it...
> > > 
> > > iirc, we currently we hardcode wext in NM code. How about adding a keyfile
> > > config that users could use to switch to nl80211 until we feel confident
> > > that it's good enough for everyone?
> > 
> > commit d27df100b587dd95f3256a8baf9db0c5d4380089 in wpa_supplicant allows
> > you to do that by editing the service file.
> that is funny, when I asked for a global command line switch for
> choosing a different driver, the argument was that the application
> adding the interface is suppose to do it by itself. Now we can do it in
> the service file. Never the less ConnMan got its own switch to choose
> which driver will be used. Does help a lot in testing and is way easier
> since you don't have to restart wpa_supplicant all the time.

In reality, NM upstream will just switch over one day and distros that
use shitty and/or proprietary drivers will need to either (a) fix them,
or (b) patch NM to use wext locally.  That's how progress gets made.


More information about the Hostap mailing list