Stefan Sperling wrote:
> On Sat, Sep 11, 2021 at 04:29:58PM +0200, Stefan Hagen wrote:
> > Sep 11 15:52:39 x13 /bsd: iwx0: associated with e6:63:da:7e:f8:24 ssid
> > "DiscMate" channel 36 start MCS 0 long preamble short slot time HT enabled
> > Sep 11 15:52:39 x13 /bsd: iwx0: missed beacon threshold set to 30 beacons,
> > beacon interval is 100 TU
> > Sep 11 15:52:39 x13 /bsd: iwx0: received msg 3/4 of the 4-way handshake
> > from e6:63:da:7e:f8:24
> > Sep 11 15:52:39 x13 /bsd: iwx0: sending msg 4/4 of the 4-way handshake to
> > e6:63:da:7e:f8:24
> > Sep 11 15:52:39 x13 /bsd: iwx0: RUN -> ASSOC
>
> Looks like the AP sent a dis-assoc frame here. I wonder why.
> Are your access points configured for band steering, perhaps?
> Or are there any other similar fancy "non-standard" enhancements
> enabled on the AP side?
I'm not sure. Because I see conflicting options here:
On each AP individually:
- Band Steering: off
In the controller software:
- [x] Connect high performance clients to 5 GHz only (beta)
There's no documentation about it. The internet describes it as
"super-duper-band-steering" that forces "modern devices" to 5G
or no connectivity at all.
I will turn this off and see if the dis-assoc disappears.
> > Sep 11 15:52:39 x13 /bsd: iwx0: sending assoc_req to e6:63:da:7e:f8:24 on
> > channel 36 mode 11n
> > Sep 11 15:52:39 x13 /bsd: iwx0: ASSOC -> RUN
> > Sep 11 15:52:39 x13 /bsd: iwx0: associated with e6:63:da:7e:f8:24 ssid
> > "DiscMate" channel 36 start MCS 0 long preamble short slot time HT enabled
> > Sep 11 15:52:39 x13 /bsd: iwx0: missed beacon threshold set to 30 beacons,
> > beacon interval is 100 TU
>
> I suspect we don't handle RUN -> ASSOC -> RUN transitions correctly.
> This somehow results in the following fw error and the already known:
> "iwx0: could not remove MAC context (error 35)
> This error has been reported before (e.g. by jmc).
> So it's not a regression.
>
> This is an interesting trace. Thanks!
Happy to help!
Best regards,
Stefan
