On Sunday, 7 February 2021 18:42:42 CET Ben Greear wrote: > Somewhere along the way I fixed up raw transmit in my firmware, so possibly > only then will vlans really have a chance of working. The first step was to disable the check which enables AP_VLAN conditional and just enable it all the time. I've started testing with firmware-5-full-community-commit-0317-cf4991294.bin but it doesn't provide the raw support + per packet swcrypto. So I've tried to switch to firmware-5-full-community-commit-1187-774502ee5.bin but it has exactly the same with the raw mode - but at least advertises WMI_SERVICE_PER_PACKET_SW_ENCRYPT. So my first target was to figure out what was the first firmware with WMI_SERVICE_PER_PACKET_SW_ENCRYPT. So you would guess that bisect would be suitable for this - but no, the first step directly found a crashing version. I should not complain so much -- just have to skip more and have no extra test results regarding the mcast support for them. Here is the log until I found the first one which is supposed to support WMI_SERVICE_PER_PACKET_SW_ENCRYPT: # has_sw_encrypt: firmware-5-full-community-commit-1187-774502ee5.bin # no_sw_encrypt: firmware-5-full-community-commit-0317-cf4991294.bin # skip: firmware-5-full-community-commit-0775-bb7462f22.bin # skip: firmware-5-full-community-commit-0782-c66b3495b.bin # no_sw_encrypt: firmware-5-full-community-commit-0533-4597878a6.bin # no_sw_encrypt: firmware-5-full-community-commit-0885-2d9cfe00b.bin # no_sw_encrypt: firmware-5-full-community-commit-1045-817be3ee8.bin # has_sw_encrypt: firmware-5-full-community-commit-1112-68b46f73e.bin # no_sw_encrypt: firmware-5-full-community-commit-1077-44c74a25a.bin # has_sw_encrypt: firmware-5-full-community-commit-1093-3c7065550.bin # no_sw_encrypt: firmware-5-full-community-commit-1085-c1d37213a.bin # no_sw_encrypt: firmware-5-full-community-commit-1089-1fbfebf26.bin # has_sw_encrypt: firmware-5-full-community-commit-1091-3aa26dbdd.bin # no_sw_encrypt: firmware-5-full-community-commit-1090-7cfbf3e6a.bin # first has_sw_encrypt commit: firmware-5-full-community-commit-1091-3aa26dbdd.bin None of the firmware version seem to have working multicast tx. And here are some (not so random) picked ones (just so nobody can say that I didn't check in the other direction): # no_per_patcket_sw_encrypt_no_mcast: firmware-5-full-community-commit-0425-a422b044f.bin # no_per_patcket_sw_encrypt_no_mcast: firmware-5-full-community-commit-0371-157623ac0.bin # no_per_patcket_sw_encrypt_no_mcast: firmware-5-full-community-commit-0344-8b9e4442a.bin # no_per_patcket_sw_encrypt_no_mcast: firmware-5-full-community-commit-0331-5259fada9.bin # no_per_patcket_sw_encrypt_no_mcast: firmware-5-full-community-commit-0324-e6723f0f6.bin # no_per_patcket_sw_encrypt_no_mcast: firmware-5-full-community-commit-0321-814d9dc06.bin # no_per_patcket_sw_encrypt_no_mcast: firmware-5-full-community-commit-0319-ef95e743e.bin # no_per_patcket_sw_encrypt_no_mcast: firmware-5-full-community-commit-0318-51cd44bdd.bin I didn't do a complete sweep of the builds but at the moment it looks a little bit like there might not be a single one which supports multicast over this setup. If you think there is a specific firmware version which I should test then just say which version. So I've decided to try the ath10k firmware blobs from Kalle's repository to provide at least something useful for someone who also has this problem and searches for a compatible version: firmware blob | works | PER_PACKET_SW_ENCRYPT ----------------------------------------------+-------+---------------------- 3.2/firmware-5.bin_10.4-3.2-00080 | N | N 3.2.1/firmware-5.bin_10.4-3.2.1-00004 | N | N 3.2.1/firmware-5.bin_10.4-3.2.1-00005 | N | N 3.2.1/firmware-5.bin_10.4-3.2.1-00007 | N | N 3.2.1/firmware-5.bin_10.4-3.2.1-00015 | N | N 3.2.1/firmware-5.bin_10.4-3.2.1-00018 | N | N 3.2.1/firmware-5.bin_10.4-3.2.1-00023 | N | N 3.2.1/firmware-5.bin_10.4-3.2.1-00024 | N | N 3.2.1/firmware-5.bin_10.4-3.2.1-00026 | N | N 3.2.1/firmware-5.bin_10.4-3.2.1-00028 | N | N 3.2.1/firmware-5.bin_10.4-3.2.1-00029 | N | N 3.2.1/firmware-5.bin_10.4-3.2.1-00031 | N | N 3.2.1/firmware-5.bin_10.4-3.2.1-00033 | N | N 3.2.1/firmware-5.bin_10.4-3.2.1-00037 | N | N 3.2.1/firmware-5.bin_10.4-3.2.1-00042 | N | N 3.2.1/firmware-5.bin_10.4-3.2.1-00044 | N | N 3.2.1/firmware-5.bin_10.4-3.2.1-00047 | N | N 3.2.1/firmware-5.bin_10.4-3.2.1-00050 | N | N 3.2.1/firmware-5.bin_10.4-3.2.1-00051 | N | N 3.2.1/firmware-5.bin_10.4-3.2.1-00053 | N | N 3.2.1/firmware-5.bin_10.4-3.2.1-00058 | N | N 3.2.1/firmware-5.bin_10.4-3.2.1-00060 | N | N 3.2.1.1/firmware-5.bin_10.4-3.2.1.1-00009 | N | N 3.2.1.1/firmware-5.bin_10.4-3.2.1.1-00017 | N | N 3.2.1.1/firmware-5.bin_10.4-3.2.1.1-00019 | N | N 3.2.1.1/firmware-5.bin_10.4-3.2.1.1-00021 | N | N 3.2.1.1/firmware-5.bin_10.4-3.2.1.1-00022 | N | N 3.2.1.1/firmware-5.bin_10.4-3.2.1.1-00025 | N | N 3.2.1.1/firmware-5.bin_10.4-3.2.1.1-00028 | N | N 3.2.1.1/firmware-5.bin_10.4-3.2.1.1-00031 | N | N 3.2.1.1/firmware-5.bin_10.4-3.2.1.1-00032 | N | N 3.4/firmware-5.bin_10.4-3.4-00074 | N | N 3.4/firmware-5.bin_10.4-3.4-00082 | N | N 3.4/firmware-5.bin_10.4-3.4-00104 | N | N 3.5.3/firmware-5.bin_10.4-3.5.3-00053 | N | N 3.5.3/firmware-5.bin_10.4-3.5.3-00057 | Y | Y 3.5.3/firmware-5.bin_10.4-3.5.3-00078 | Y | Y 3.6/firmware-5.bin_10.4-3.6-00140 | Y | Y Kind regards, Sven