[msoengineer]

Might someone else see if they can get a 5ghz virtual Access Point to work on their router using any recent November 2019, December 2019, or preferably 12-06-2019-r41664 specifically?

The symptoms I get when creating a VAP is that the 5ghz radio will "die." My WiFi status will show the following:

Chipset QCA9984 802.11ac
RadioRadio is- On
Mode- AP
Network- AC/N-Mixed
SSID- XXXXXXX
Channel- Unknown
Busy Time- 0 ms
Active Time- 0 ms
TX Power- 30 dBm
Rate- Auto
ACK Timing- 21µs (3150m)
Encryption - Interface ath0Enabled, WPA2-PSK
Connected- Clients 0

Neither the regular 5ghz SSID nor 5ghzVap will show up on any wifi scanning software.

I need some more data points from other users.

Router model:
Build:
Then copy from the Status>wireless Tab:

Chipset QCA9984 802.11ac
RadioRadio is On
ModeAP
NetworkAC/N-Mixed
SSID
Channel149 + 155 (5745 MHz VHT80)

Thanks in Advance!

[msoengineer]

Back in 2018 the writers of the ATH10k firmware decided that if you run multiple VAP's then you should use a beacon >=100... setting it lower will stop the radio from broadcasting. Problem is solved thanks to BS and he will make a commit to not allow you to enter <100 when using a VAP.

https://patchwork.kernel.org/patch/10603777/

Thank you BS!

QCA wireless wiki was updated to reflect this issue.

[egc]

If I am not mistaken the beacon interval is reset to 100 if it is set lower, I now use your recommendation and set it 67.

So maybe we should change that to 101?

[blkt]

[msoengineer]

I think values less than 100 work fine, so long as you don't use/create a VAP. If you plan to run a VAP you need to have it at 100 as a minimum.

FWIW, I am using 101 since that's a prime number.

Again, set which ever radio you want to be "primary," first to be seen, with the lower beacon, bacon, interval.

Bacon makes everything better!

[blkt]

[msoengineer]

[kernel-panic69]

^^^^^^ I wasn't gonna say it

[egc]

Any decent programming language would have known you meant an integer and not a string