Re: [patch] _always_ need AP_SCAN 1 for madwifi

On Tue, 2006-02-07 at 17:57 -0500, Dan Williams wrote:

> I know that something working needs to get shipped soon, but at some
> point here we need to push back against upstream drivers to make them
> clean up their stuff...  Everything else seems to work OK with ap_scan =
> 2 (which is essentially just 'iwconfig ath0 essid foobar', and should
> make the driver trigger a scan internally).  I wonder why madwifi needs
> it's own toys and can't just share like the rest of the children.

I don't know either - but we reproduced it on several machines.  madwifi
is just stupid.

If we use "AP_SCAN 2" simply to reduce association time, it might not be
insane to use "AP_SCAN 1" all of the time.  It isn't a device-dependent

	Robert Love

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