On 2019-12-31 15:00, Stefan Sperling wrote:
> iwn(4) taking several scan attempts to find 5GHz APs is a known issue.
> The driver relies on the firmware for this. I have already tried to fix
> this problem but never got anywhere. If you want to give it another
> attempt then try playing with the channel dwell timing paramters the
> driver sends in the scan command. Maybe you can find values that make
> it work every time?
With this in mind I tried 2.4, but I couldn't get that to work at all with or
without a join list.
Dec 31 17:23:51 mechanicum /bsd: iwn0: end active scan
Dec 31 17:23:51 mechanicum /bsd: iwn0: - 18:0f:76:04:98:32 11! +199 54M ess
privacy rsn "TALKTALK049832"!
Dec 31 17:23:51 mechanicum /bsd: iwn0: + 20:39:56:59:7a:b7 8 +225 54M ess
privacy rsn "Ryo"
Dec 31 17:23:51 mechanicum /bsd: iwn0: - 24:a7:dc:54:ae:e2 6! +189 54M ess
privacy rsn "SKYB4F43"!
Dec 31 17:23:51 mechanicum /bsd: iwn0: - 3c:89:94:24:0a:4a 6! +189 54M ess
privacy rsn "SKYG6NEF"!
Dec 31 17:23:51 mechanicum /bsd: iwn0: - 78:32:1b:ab:c2:9c 11! +206 54M ess
privacy rsn "TALKTALKABC29C"!
Dec 31 17:23:51 mechanicum /bsd: iwn0: - 90:02:18:61:72:54 6! +187 54M ess
privacy rsn "SKYG6NEF"!
Dec 31 17:23:51 mechanicum /bsd: iwn0: - a0:bd:cd:e2:54:da 1! +200 54M ess
privacy rsn "SKYKENXR"!
Dec 31 17:23:51 mechanicum /bsd: iwn0: - d0:57:94:a4:36:1a 1! +190 54M ess
privacy rsn "BTHub6-C8T9"!
Dec 31 17:23:51 mechanicum /bsd: iwn0: - d0:57:94:cb:a2:3a 11! +173 54M ess
privacy rsn "BTBHub6-7G6F"!
Dec 31 17:23:51 mechanicum /bsd: iwn0: - d2:57:94:a4:37:19 36! +169 54M ess
privacy rsn! "BTWifi-X"!
Dec 31 17:23:51 mechanicum /bsd: iwn0: - d2:57:94:a4:38:1b 1! +190 54M ess
no! rsn! "BTWifi-with-FON"!
Dec 31 17:23:51 mechanicum /bsd: iwn0: - d2:57:94:cb:a4:3b 11! +173 54M ess
no! rsn! "BTWi-fi"!
Dec 31 17:23:51 mechanicum /bsd: iwn0: SCAN -> AUTH
Dec 31 17:23:51 mechanicum /bsd: iwn0: sending auth to 20:39:56:59:7a:b7 on
channel 8 mode 11g
Dec 31 17:23:51 mechanicum /bsd: iwn0: AUTH -> ASSOC
Dec 31 17:23:51 mechanicum /bsd: iwn0: sending assoc_req to 20:39:56:59:7a:b7
on channel 8 mode 11g
Dec 31 17:23:55 mechanicum /bsd: iwn0: association timed out for
20:39:56:59:7a:b7
Dec 31 17:23:55 mechanicum /bsd: iwn0: ASSOC -> SCAN
Dec 31 17:23:56 mechanicum /bsd: iwn0: end active scan
After using 5G I tried 2.4 again and it worked first time (after a few scans
where Ryo did not appear and the first still showed channel 44 whilst AP was
switched).
Clearly Ryo is dropping out of sight for some reason. Perhaps I will dwell on
it. I assume that involves building a kernel each time? Maybe I can try some
parameters once per use.
