DanielRIOT
commented
3 years ago Looks like I'm getting a similar issue - Trying to get Mesh mode on a Compex WLE900VX ( QCA9880 hw2.0 )
Build is Master (OpenWrt SNAPSHOT, r14966-7330348f2d on IPQ806x) using ath10k-firmware-qca988x-ct-full-htt
cat /sys/kernel/debug/ieee80211/phy2/ath10k/firmwa
re_info
directory: ath10k/QCA988X/hw2.0
firmware: ct-firmware-2.bin
fwcfg: fwcfg-pci-0002:01:00.0.txt
bus: 0002:01:00.0
features: wmi-10.x,mfp,txstatus-noack,wmi-10.x-CT,ratemask-CT,regdump-CT,txrate-CT,flush-all-CT,pingpong-CT,ch-regs-CT,nop-CT,set-special-CT,get-temp-CT,tx-rc-CT,cust-stats-CT,retry-gt2-CT,txrate2-CT,beacon-cb-CT,wmi-block-ack-CT
version: 10.1-ct-8x-__fH-022-538f0906
hw_rev: 988x
board: board.biniw shows that it should support mesh, but it isn't listed as a valid interface combination
iw phy2 info:
...
Supported interface modes:
* IBSS
* managed
* AP
* AP/VLAN
* monitor
* mesh point
* P2P-client
* P2P-GO
* P2P-device
...
Supported TX frame types:
* IBSS: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
* managed: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
* AP: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
* AP/VLAN: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
* mesh point: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
* P2P-client: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
* P2P-GO: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
* P2P-device: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
Supported RX frame types:
* IBSS: 0x40 0xb0 0xc0 0xd0
* managed: 0x40 0xb0 0xd0
* AP: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0
* AP/VLAN: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0
* mesh point: 0xb0 0xc0 0xd0
* P2P-client: 0x40 0xd0
* P2P-GO: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0
* P2P-device: 0x40 0xd0
...
valid interface combinations:
* #{ managed, P2P-client } <= 16, #{ P2P-GO } <= 3, #{ AP } <= 16, #{ IBSS } <= 1,
total <= 16, #channels <= 1, STA/AP BI must match, radar detect widths: { 20 MHz (no HT), 20 MHz, 40 MHz, 80 MHz }The other card ( WLE1216V2 - QCA9884 ) IW output is the same for the supported TX and RX frames and interface modes, but the valid interface combinations section show "Mesh" ( not P2P ,.. interesting but irrelevant at the moment )- they are running 10.4-ct vs 10.1-ct and are also different chipsets ( 9884 vs 9880 ) on the WLE1216V2:
valid interface combinations:
* #{ managed } <= 16, #{ AP, mesh point } <= 16, #{ IBSS } <= 1,
total <= 16, #channels <= 1, STA/AP BI must match, radar detect widths: { 20 MHz (no HT), 20 MHz, 40 MHz, 80 MHz, 80+80 MHz, 160 MHz }
Description of the problem (how to configure, how to reproduce, how often it happens).
I have two devices: Ubiquiti nano station and Ubiquiti Mesh AC, both (QCA 988x). Driver is loaded fine, once I set both in IBSS mode (no encryption and did not use wpa_supp) the kernel crashes and log is filled with "ath10k_pci 0000:00:00.0: SWBA overrun on vdev 0, skipped old beacon" messages on both units. Also, the units cannot ping.
Software (OS, Firmware version, kernel, driver, etc) OpenWRT, 4b403821c6e on master.
Logs (dmesg, maybe supplicant and/or hostap)