Hellou

I saw in the change logs a while ago that mikrotik as client (station) and mikrotik as ap (ap) should support seamless roaming.

simple setup, 1 router and 4 aps.

So i ordered 4 aps
cAP ax as aps - they are running with transmit power of 11 and are around 10 - 12 meters apart.

1 hap ax2 to be the caps man (router at the same time)
Setup things, everything works, aps joined , configuration is redistibuted , wifi is online and i can reach sites from it... no problem there.

So i tried one hap ac2 as client (station) to connect to the aps.
ac2 connects , but when it roams its takes second to roam from one ap to another , even ping or two drops. As far as i can tell this is the same behavior as with any other enterprise APs (for example unifi or ruckus).

So how to turn on the seamless roaming ?

there are option for the "FT" that are on...off... browsed the forum , tried that , tried some stuff in security profiles.... was changing thing for the past few hours , eventually gave up and trying here what could go wrong.

[admin@router] > /export
# 2025-05-09 12:32:03 by RouterOS 7.19beta8
# software id = XNJL-5BWV
#
# model = C52iG-5HaxD2HaxD
# serial number = HEF08SVM6ZQ
/interface bridge
add admin-mac=48:A9:8A:C4:56:8E auto-mac=no comment=defconf name=bridge vlan-filtering=yes
/interface vlan
add interface=bridge name=vlan1 vlan-id=1
add interface=bridge name=vlan2 vlan-id=2
/interface list
add comment=defconf name=WAN
add comment=defconf name=LAN
/interface wifi datapath
add bridge=bridge disabled=no name=vlan1 vlan-id=1
add disabled=no name=vlan2 vlan-id=2
/interface wifi configuration
add channel.band=2ghz-ax country=Slovakia datapath=vlan1 disabled=no mode=ap name=caps-vlan1-test security.authentication-types=wpa2-psk .encryption=ccmp,gcmp,ccmp-256,gcmp-256 ssid=caps-vlan1-test tx-power=11
add channel.band=5ghz-ac country=Slovakia datapath=vlan2 disabled=no dtim-period=1 manager=capsman-or-local mode=ap name=caps-vlan2-test security.authentication-types=wpa2-psk .connect-group=vlan2_group .connect-priority=0/1 .encryption=\
ccmp,gcmp,ccmp-256,gcmp-256 .ft=yes .ft-mobility-domain=0xADC4 .ft-over-ds=yes .group-encryption=ccmp ssid=caps-vlan2-test tx-power=11
/interface wifi steering
add disabled=no name=steering_rrm_wnm neighbor-group=dynamic-caps-vlan2-test-e0cd6932 rrm=yes wnm=yes
/ip pool
add name=default-dhcp ranges=10.90.1.150-10.90.1.190
add name=vlan2-pool ranges=10.90.2.150-10.90.2.200
/ip dhcp-server
add address-pool=default-dhcp interface=vlan1 name=defconf
add address-pool=vlan2-pool interface=vlan2 name=vlan2-dhcp
/disk settings
set auto-media-interface=bridge auto-media-sharing=yes auto-smb-sharing=yes
/interface bridge port
add bridge=bridge comment=defconf interface=ether2
add bridge=bridge comment=defconf interface=ether3
add bridge=bridge comment=defconf interface=ether4 pvid=2
add bridge=bridge comment=defconf interface=ether1
add bridge=bridge comment=defconf interface=*2
add bridge=bridge comment=defconf interface=*3
/ip neighbor discovery-settings
set discover-interface-list=LAN
/interface bridge vlan
add bridge=bridge tagged=ether1,ether2,ether3 untagged=ether4 vlan-ids=2
/interface list member
add comment=defconf interface=bridge list=LAN
add comment=defconf interface=ether5 list=WAN
add interface=vlan2 list=LAN
add interface=vlan1 list=LAN
add interface=*22 list=LAN
add interface=*23 list=LAN
/interface wifi capsman
set certificate=auto enabled=yes interfaces=vlan1 package-path="" require-peer-certificate=no upgrade-policy=none
/interface wifi provisioning
add action=create-dynamic-enabled disabled=no master-configuration=caps-vlan1-test supported-bands=2ghz-ax
add action=create-dynamic-enabled disabled=no master-configuration=caps-vlan

also is there a function to load-balance ? like on this ap there are 7 clients , but on the ap that is right next to it can clients have still the same or slightly worse signal is only 1 , so move there few clients "handover" .. ?

Thank you

On the ac2 you'll need wifi-qcom-ac and you need to enable station-roaming and wnm for FT support as a station

On the ac2 you'll need wifi-qcom-ac and you need to enable station-roaming and wnm for FT support as a station

THX man, will try that, would be awesome if that works

nope, the new wireless-qcom-ac does not seems to be capable of roaming at all, or at least its not showing in the logs and does not behavie like that...

with the wireless i could see roaming messages in the client (hap ac2) , roaming started around -73... took second - still not a seamless roam...
i also could see on the caps manager that roaming occured

with wireless-qcom-ac , i cant see the message , only hard disconnects that occured at -81 signal levels...
also from the caps manager disconnected , connection lost with signal strength

this is the only part thats important on the client, already tried to add more from other posts that helped... but... i am not really seeing here even basic functionality...

# model = RBD52G-5HacD2HnD
# serial number = HD4087DYH9W
/interface bridge
add admin-mac=18:FD:74:A3:D3:1C auto-mac=no comment=defconf name=bridge port-cost-mode=short
/interface list
add comment=defconf name=WAN
add comment=defconf name=LAN
/interface lte apn
set [ find default=yes ] ip-type=ipv4 use-network-apn=no
/interface wifi security
add disabled=no encryption=ccmp,gcmp,ccmp-256,gcmp-256 ft=yes ft-over-ds=yes name=caps_sec
/interface wifi
set [ find default-name=wifi2 ] configuration.mode=station .ssid=caps-vlan2-test .station-roaming=yes disabled=no security=caps_sec security.connect-priority=0/1 \
.ft=yes .ft-over-ds=yes steering.rrm=yes .wnm=yes
/ip pool

Very likely unrelated to the issue at hand but there are a couple of possible problems in your Ax2 configuration.

1. don't use vlan 1 unless you really know what you are doing
viewtopic.php?t=215004

2. you have a few places where *something* has been replaced by an * (asterisk) followed by a (hex) number, these are leftovers, references to things that have been removed or renamed, see point #21 here:
viewtopic.php?p=1128345

Very likely unrelated to the issue at hand but there are a couple of possible problems in your Ax2 configuration.

1. don't use vlan 1 unless you really know what you are doing
viewtopic.php?t=215004

2. you have a few places where *something* has been replaced by an * (asterisk) followed by a (hex) number, these are leftovers, references to things that have been removed or renamed, see point #21 here:
viewtopic.php?p=1128345

i dont use vlan1 , well in example there is but vlan 2 is being used for tests...etc..
regarding the second point , i did not used any blocks of scripts / ready made commands, i just watched the video of mikrotik guy doing the setup and those were the steps i did

also some not mentioned tweaking on the ap side so the vlans do work properly, like vlan filtering, adding vlans to the bridge...etc...

but i guess i might burn it down and build it a new to see what happens,