Still no ipv6 fastpath 
If you deactivate 2.4, are the devices able to connect to 5?
I had the same problem and in the end it was my devices fault because they didn’t “see” channels above 100.
2.4/5 GHz roaming works great in my case.
I expected it to be something like “::/0&52308:1000”
Roaming works fine for me when I’m at distance of router, but devices close to router are doing stupid things which they didn’t before in 7.14 and all versions before.
As I said , devices roam from 5ghz to 2ghz, so yes they can connect, sometimes they are connected for hours then suddenly all roam to 2ghz, it must be router sending something, no way multiple different vendor devices decided to roam same time unless roaming protocol on mikrotik did send something..
This was good too:
*) bridge - added dynamic tagged entry when VLAN interface is created on vlan-filtering bridge;
It even put comments on in /interface/bridge/vlan on what triggered the “D” dynamic vlan entry there, i.e. “added by pvid”, “added by vlan on bridge”, …
Ah OK, then maybe it depends on the DFS.
What 5GHz channel are you using?
USE
WiFi Security → FT(TAB) → FT Enabled = YES
Should fix that for you
Not using dfs, no radar detects,5220.
Enabled day one.
IS-IS towards Cisco no longer works on ptp , only broadcast
Is anyone can tell slow and unstable autoneg with XL710 already fixed?
Also with Huawei not working on p2p Level 2.
Are there any plans to bring features of wifi-qcom**-ac** on par with wifi-qcom … the list of differences is growing with every new ROS version …
Probably not possible without bloating the size of the package, thus causing more problems for devices like hAP ac². wifi-qcom is over 3.5x the size of wifi-qcom-ac.
So sad 
Until Mikrotik decides to provide the correct level of logging for Wifi, and especially roaming/band steering etc. you won’t be able to understand what is going on.
And as such won’t know what to do and if behavior is correct.
Another missing option is to be able to set steering thresholds etc.
I already reduced 2ghz to 10 TX which is over 10db difference from 5ghz, dont know what else to do.
maybe a stupid workaround : allow devices to connect to 2.4GHz only if signal is WEAKER than let’s say -75dBm. While it seems like very skewed logic, let me try to explain : you have approx. 10dBm difference between TX Power of 5GHz and 2.4GHz radios. That, together with slighly worse propagation compared to 5GHz, should mean that only devices which are approx. -85dBm signal on 5GHz will roam and stay on 2.4ghz : when “non-warranted” client connects to 2.4GHz (that is, a client that should not be connected to 2.4GHz) and the device has signal stronger than -75dBm, it will be rejected by 2.4GHz and it should reconnect back to 5GHz.
When it has -75dBm signal on 2.4GHz, it should have around -85dBm or less on 5GHz. Set this threshold per your local conditions, don’t know what throughput you achieve on 5GHz with -80/-85dBm signal, don’t know what you have at 2.4GHz/-75dBm. Test it out.
Sure, when such client decides to roam unnecessarily, there will be slight disruption of communication. A network outage. Correct.
The question is, if that makes a real problem for you once in a couple of hours as you said - for me, it would not be any problem at all.
Next option would be to question roaming generally : do you really need that ? Make those networks independent, connect to 2.4GHz only when necessary. Connect low-throughput devices AND DISTANT devices to 2.4GHz (air conditioning units, Alexa, intelligent house appliances…) and keep them there (no roaming at all), dedicate 5GHz for high-throughput / low-latency devices only. Don’t roam.
Yeah, but i dont want to do any workarounds when i just can just revert to 7.14.3 and i dont have any problems… Fact is new Qualcomm drivers in 7.15 messed up allot of stuff regarding wireless…
And as i said, i dont have problem at those signal levels, problem is ONLY for devices very next to router, my devices roam from (-30 db 5ghz) to (-20db 2ghz), that is the problem…
Im running 2ghz on 10tx and 5ghz on 24tx now, before on 7.14 i ran 16tx and 22tx and never devices preferred or roamed to 2ghz at such high levels of signal..
Actually you shouldn’t enable FT unless using CAPsMAN and multiple APs…
Not quite. It can also be used for roaming between radios of the same AP provided same SSID is used.
*) l3hw - added per-VLAN packet and byte counters to compatible switches;
That is very interesting!
Where are these values showed? In which cli command branch?
Thanks.