I applied one of this patch [
0002-DNM-DSA_Bridge_FDB_Sync_Workaround.patch
With no changes, but I found something else -- which might be my problem -I just don't have a solution yet.
I do have two routers configured with the same SSID and I can still under 4.19 Kernel walk from one area to the other and they handover the signal --> I would not even know about the handshake.
What I noticed today is. That the kernel 5.4.80 works when I start my computer close to the WRT3200 with 5.4.80 kernel and it changes over to the other one (EA8500) perfect. But when I walk back to the WRT3200 I don't get an IP only when I reboot my computer (by the way an apple MacBook air) I will get an IP.
So I turned DHCP on the WRT3200ACM for different IP's than my main router I do get an IP when I walk from one to the other router, but can't connect to the internet or main router anymore until I reboot. This might not have anything todo with mwlwifi but the DSA setup and the new 5.4.80 kernel. I have the setup identical to the 4.19 setup except the switch setup is not there (as it should not).
What does rebooting change when I go to the other area (I also have the same effect on my phone)
Should I just wait for a new kernel to be released for the WRT3200ACM?
Thanks for all the help so far.
If I just move from the EA8500 to the WRT3200 i can not get an ip but after around 5 minutes I will get one and everything works
So one of your link describes exactly the problem.
For that the node's clients roaming from one of its Lan ports to a Wlan port are not able to receive traffic from the Lan ports until the switch's ATU ageing register (default ~ 300 seconds) clears the roamed client's MAC, as it remains unaware that the client has moved to another port (Wlan) and therefore drops traffic for that client's MAC.