EScan was not including band in chanspec conversion during prep, causing it to only scan 2g channels by default.

AsahiLinux / linux

Linux kernel source tree

Other

2.17k stars 84 forks source link

EScan was not including band in chanspec conversion during prep, causing it to only scan 2g channels by default. #209

Closed dberlin closed 8 months ago

dberlin commented 8 months ago

It would run through all channels, but only construct 2g band chanspecs for them. We would discover BSSID's on other bands only through passive scans/etc.

Fixed by having chanspec used during escan prep, and verifying it now sees 2g/5g/6g in escan.

Signed-off-by: Daniel Berlin dberlin@dberlin.org

marcan commented 8 months ago

Manually cherry-picked, thanks!