Problem with STA re-association when AP changes capabilities.

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

 



I am seeing some funny behavior with stations reconnecting to an AP.

Both STA and AP are running a recent hostap build, with some custom patches on top.

My test case is to configure the AP for /a mode (it is on an /AC radio), and associate
the station.

If I then quickly restart the AP configured for /n mode, I would expect that the STA would
then connect with HT enabled.  However, what I notice is that it stays at /a rates.  Probably
this is because it did not rescan.  Here is an iw event log of this:


2019-02-19 14:31:29.629  1.2:  vap0000: del station 18:00:db:38:84:9c
2019-02-19 14:31:29.629  1.2:  vap0000 (phy #0): stop AP

# I guess maybe the AP doesn't manage to get deauth frames on the air.  That could
# be bugs/limitations/races in my ath10k driver and/or firmware, or how I am killing
# the VAP I suppose.

2019-02-19 14:31:42.619  1.1:  sta0000: del station 04:f0:21:2b:e7:35
2019-02-19 14:31:42.620  1.1:  sta0000 (phy #3): deauth 04:f0:21:2b:e7:35 -> 18:00:db:38:84:9c reason 7: Class 3 frame received from non-authenticated station
2019-02-19 14:31:42.620  1.1:  sta0000 (phy #3): disconnected (by AP) reason: 7: Class 3 frame received from non-authenticated station
2019-02-19 14:31:42.622  1.1:  sta0000: new station 04:f0:21:2b:e7:35
2019-02-19 14:31:42.622  1.1:  regulatory domain change: set to world roaming by the wireless core upon initialization request
2019-02-19 14:31:42.623  1.2:  vap0000: new station 18:00:db:38:84:9c
2019-02-19 14:31:42.623  1.1:  sta0000 (phy #3): auth 04:f0:21:2b:e7:35 -> 18:00:db:38:84:9c status: 0: Successful
2019-02-19 14:31:42.625  1.1:  regulatory domain change: set to US by a user request
2019-02-19 14:31:42.724  1.1:  sta0000 (phy #3): assoc 04:f0:21:2b:e7:35 -> 18:00:db:38:84:9c status: 0: Successful
2019-02-19 14:31:42.724  1.1:  sta0000 (phy #3): connected to 04:f0:21:2b:e7:35
2019-02-19 14:31:42.725  1.1:  IFNAME=sta0000 <3>CTRL-EVENT-CONNECTED - Connection to 04:f0:21:2b:e7:35 completed [id=0 id_str=]
2019-02-19 14:31:42.725  1.1:  phy #3: regulatory domain change: set to US by a country IE request on phy3


So, is it OK that the station did not re-scan the AP and/or automatically refresh its beacon
info with the new capabilities?

Thanks,
Ben

--
Ben Greear <greearb@xxxxxxxxxxxxxxx>
Candela Technologies Inc  http://www.candelatech.com


_______________________________________________
Hostap mailing list
Hostap@xxxxxxxxxxxxxxxxxxx
http://lists.infradead.org/mailman/listinfo/hostap



[Index of Archives]     [Linux Wireless]     [Linux Kernel]     [ATH6KL]     [Linux Bluetooth]     [Linux Netdev]     [Kernel Newbies]     [IDE]     [Security]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux ATA RAID]     [Samba]     [Device Mapper]

  Powered by Linux