Коренберг Марк

Both firmwares are the same: `QCA988X-firmware-2-ct-full-htt-mgt-community-22.bin.lede.007`

CT-driver is from commit a696e602a0fc83dd809e5860e21019cf48e0028b and subdir for 4.16 kernel.

supplicant.conf: ``` # =============== country=RU ctrl_interface=/var/run/wpa_supplicant ap_scan=2 eapol_version=2 network={ # =============== ht40=1 max_oper_chwidth=1 frequency=5180 fixed_freq=1 vht=1 ssid="S_a23a6db169687f67fe925a5819a1" proto=RSN group_rekey=86400 wpa_ptk_rekey=86400 key_mgmt=SAE sae_password="d7adf86b1d126ff8853cceea1a12bd95" mode=1 scan_ssid=0 pairwise=CCMP group=CCMP disable_max_amsdu=1 bssid=42:27:5a:5a:0e:14 beacon_int=100 }...

@greearb ping. Please tell the status.

@greearb We actually have exactly the same problems on wave-2 chip (encrypted MESH does not work without setting beacon_int=10). And when it works, speed is much slower (i.e. 100 mbti/sec)...

@greearb CT-firmware + IBSS + beacon_int=10 gives about 120 mbit/sec QCA firmware + 802.11s gives less than 100. in my setup. Anyway. I will follow your instructions how to debug....

Driver has a comment: ``` /* FIXME: Current unchaining logic can only handle simple case of raw * msdu chaining. If decapping is other than raw the chaining may be...

@greearb RX_MSDU_DECAP_NATIVE_WIFI. I can not check right now (will check if you insist on), but as far as I remember, yes, it reproduces with AP mode.

@greearb https://github.com/torvalds/linux/blob/9c7db5004280767566e91a33445bf93aa479ef02/drivers/net/wireless/ath/ath10k/core.c#L2220 Maybe this line should be changed ? Also, seems `echo 1 64 > /sys/kernel/debug/ieee80211/phy0/ath1 0k/htt_max_amsdu_ampdu` does not work.

Yes but we may prepare internal structures of the library for that change. See https://git.netfilter.org/libmnl/log/?h=nl-mmap for example.