Here's a bunch of scan fixes:


There's a few things in here:

* Add extra code to verify A-MPDU TX sequence numbers make sense;
* Fetch the flags TLV from the firmware if it provides it;
* CRC threshold changes for the later NICs (apparently to prevent
firmware crashes? Who knows!);
* Track if a scan command is in flight and if so, don't issue another
RXON or SCAN until it's finished or we reset the NIC;
* Lots of changes to the scan command values - set
passive/active/dwell correctly, set a maximum dwell time.

It turns out that we were doing a lot of very bad things in the scan
command and if you squinted at the firmware incorrectly, it could just
plain never return from a scan on a passive channel.

I've tested this on my 5100 and the scan stability has improved. The
main issue I see here now is the net80211 related scan issue, not the
driver scan issue. There's one driver issue I think still exists -
where the session disassociates during an active scan. I'm not yet
sure why this.

There are some other things to fix - I'll post patches to that once
I've committed this scan stuff. Specifically - iwlwifi on Linux does a
single-channel scan (to a different frequency band to the active one)
occasionally to reset/retune the radio. I'll look into this later.


freebsd-wireless@freebsd.org mailing list
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"

Reply via email to