Bug 163574

Summary:	[net80211] overly-frequent HT occupancy changes
Product:	Base System	Reporter:	Adrian Chadd <adrian>
Component:	wireless	Assignee:	freebsd-wireless (Nobody) <wireless>
Status:	Open ---
Severity:	Affects Only Me	CC:	bz
Priority:	Normal
Version:	Unspecified
Hardware:	Any
OS:	Any
Bug Depends on:
Bug Blocks:	283171

Description Adrian Chadd freebsd_committer

2011-12-23 19:40:11 UTC

When running this tplink in occupied 2.4GHz space, the AP instance frequently bounces between these states:

wlan0: [00:19:e0:66:66:68] HT bss occupancy change: 2 sta, 2 ht, 1 ht40, non-HT sta present, HT protmode now 0x13
wlan0: [00:19:e0:66:66:68] HT bss occupancy change: 2 sta, 2 ht, 1 ht40, non-HT sta present, HT protmode now 0x11
wlan0: [00:19:e0:66:66:68] HT bss occupancy change: 2 sta, 2 ht, 1 ht40, non-HT sta present, HT protmode now 0x13
wlan0: [00:19:e0:66:66:68] HT bss occupancy change: 2 sta, 2 ht, 1 ht40, non-HT sta present, HT protmode now 0x11
wlan0: [00:19:e0:66:66:68] HT bss occupancy change: 2 sta, 2 ht, 1 ht40, non-HT sta present, HT protmode now 0x13
wlan0: [00:19:e0:66:66:68] HT bss occupancy change: 2 sta, 2 ht, 1 ht40, non-HT sta present, HT protmode now 0x11
wlan0: [00:19:e0:66:66:68] HT bss occupancy change: 2 sta, 2 ht, 1 ht40, non-HT sta present, HT protmode now 0x13

. I'm not sure whether it's a problem but it is occuring very very
frequently and this may be interfering with station operation.

Fix: 

Not known.
How-To-Repeat: * enable 11n
* throw the AP into a busy 2.4ghz environment with non-11n stuff around you
* wlandebug +11n

Comment 1 Mark Linimon freebsd_committer

2011-12-24 01:01:31 UTC

Responsible Changed
From-To: freebsd-bugs->freebsd-wireless

Over to maintainer(s).

Comment 2 Eitan Adler freebsd_committer

2018-05-28 19:43:33 UTC

batch change:

For bugs that match the following
-  Status Is In progress 
AND
- Untouched since 2018-01-01.
AND
- Affects Base System OR Documentation

DO:

Reset to open status.


Note:
I did a quick pass but if you are getting this email it might be worthwhile to double check to see if this bug ought to be closed.