I just ran into the same issue. I finally upgraded from 22.05.. to 23.03.3. At first I setup fast roaming (802.11r) among 3 access points. It worked great and was easy to setup.
Then I tried to implement VLANs for a guest network. I got the VLANs all setup and working correctly, but it broke the 802.11r Fast Roaming. I get the same "key addition" errors that you mention.
I haven't been able to figure out if it's (1) a configuration issue on my end, (2) an issue with swconfig and DSA or (3) a genuine bug in OpenWrt.
For what my post might count... in case some relevant people reads it... I had and still have the same issue with the 802.11r ;
all my devices: android and linux laptop, stick to the first wifi they connect. Even if I literally next to an another and the one connected to is 1bar (very low).
I am trying 802.11r for years and never worked to me.
I hope for future development of 802.11r .
Did you try to apply recommendations from Wifi Roaming / fast transitioning not working - #11 by psherman? These things are really important and no amount of settings will force your devices to behave if this isn't done. Devices often consider roaming only below -70 - -75 dBm range, so you need to make sure that the signal level is low enough (for example -65 dBm) somewhere in the mid-point between APs.
Unfortunately some (most?) Android devices and "PC" laptops when combined with specific APs aren't great with roaming. For example: https://superuser.com/questions/1770394/how-to-get-my-linux-wi-fi-to-reliably-roam-from-ap-to-ap
This question highlights another common suggestion that sounds counter-intuitive: disable 802.11r. Roaming without it works just fine and isn't slow, contrary to what the name suggests.
By curiousity.. and by all means I dont want to start an argue about it... only interested to understand.
what is the option 802.11r implantation is?
What I mean is that there is an option to make it easier to roaming between APs.
But I read in many posts that is at bit controversial and often needed some extra tricks like change dbi...
I used Mikrotik in the past and the dbi management was an option in the roaming option; clients were actively disconnected when they where too far from an AP and closer to an other.. in turn, a client device was disconnected from an AP due to its dbi limit set.
Since Openwrt 802.11r does not seem to be as friendly as (I guess) we would expect, I would imagine that adding the dbi limit options would work better.
Now.. I have no idea if this is a complicated implementation, maybe this is why the dbi limit option is not integrated in the fast roaming 802.11r.
You can definitely make 802.11r work on OpenWrt. The purpose of this standard is to make it faster, especially in case of enterprise WiFi networks, for the station to acquire key(s) to connect to the target AP when roaming. However, this requires:
Some communication between APs, which might need to be configured.
Understanding peculiarities of the devices you have and their 802.11r implementations and again adjusting configuration to cover for that. Take a look at the link in my post above to see an example of an incompatibility.
Because this is complicated and things might not work for esoteric reasons, you need to start with the basics and have "normal" (with 802.11r disabled) roaming work first. The video posted earlier by psherman exactly shows how to do it.
802.11r doesn't make a huge amount of sense in most consumer environments where there's only a small number of APs.
2 or 3? No real benefit.
20 to 30? Maybe, but radio tuning will be more effective.
200 to 300? Now you're talking, along with carefully surveyed AP positioning and radio tuning.
2000, 3000+? Hell yeah. But get staff trained or recruited with experience first, because that sort of pervasive wireless environment has far more challenges than client roaming!
Finger in the air estimations - every single install will be different. It also depends on the number of connected clients, which will be relatively small and under some semblance of local control in a consumer environment.
Where I work we have many thousands of APs and of the order of 10k to 20k devices connected at peak times. Most of them aren't centrally managed, although their connectivity is via 802.1x. We have a highly experienced wireless networking team and I can move within and between buildings with pretty much zero loss of connection. It's all very highly tuned and constantly monitored.
The consumer and enterprise worlds are completely different, perhaps obviously and unsurprisingly.