I've been debugging an issue where my ath10k firmware is running out of key objects to allocate. This could be a simple issue in the firmware, but first I wanted to try to figure out how things are supposed to work. What I see in my firmware is that near time of association it allocates 4 keys. Two of them are multicast, and one of the multicast is index 0, the second is index 1. Then, some time later (probably on rekey), another multicast is added at index 2. After that, key space is exhausted so I see errors in the kernel logs about adding broadcast keys failing. TCP and UDP traffic continues to flow, but I am not testing multicast traffic, so maybe that would be failing. So, question is: Is it expected that the mcast keys keep being added at increasing key indexes? If so, what is the maximum index allowed? Is this something primarily controlled at the supplicant level? Thanks, Ben -- Ben Greear <greearb@xxxxxxxxxxxxxxx> Candela Technologies Inc http://www.candelatech.com -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
