Hi Normis,in capsman set these settings:
ft=yes. ft-over-ds=yes
The documentation could be MUCH clearer that distributed system = capsman, but thanks for the tip.in capsman set these settings:
ft=yes. ft-over-ds=yes
Just to clarify: FT over Distribution System (ft-over-ds) ≠ CAPsMANThe documentation could be MUCH clearer that distributed system = capsman
Are you sure your ax3 is being managed by capsman? My understanding is that local radios aren't supported.
Sorry, I said that badly... but I never wrote that hAP ax3 local wifi interfaces are managed by capsman!Are you sure your ax3 is being managed by capsman? My understanding is that local radios aren't supported.
Yes @mkx, that's exactly what happens.which is true if CAPsMAN (managing remote wifiwave2 radios) runs on same ROS as local wifiwave2 interface.
Where and how exactly should this setting be made?in capsman set these settings:
ft=yes. ft-over-ds=yes
You have two caps managed by the hAPax3 (configuration.manager=capsman) and you have the hAPax3 radios running locally, not managed by capsman (configuration.manager=local). When your client transitions from one of the caps to the local radio on the hAPax3 how can 802.11r work?Sorry I don't understand what you mean...
Yes FT works, all wifi interfaces are managed by the same instance of RouterOS.
It's been said many times and it's also written on the wiki:You have two caps managed by the hAPax3 (configuration.manager=capsman) and you have the hAPax3 radios running locally, not managed by capsman (configuration.manager=local). When your client transitions from one of the caps to the local radio on the hAPax3 how can 802.11r work?
It's not documented, but I also think the CAPsMAN manager is setting the wifi interface on the CAP, and ... is doing the authentication for the CAP's wifi interface.That's how I understand it should work.
Yes, local interfaces and provisioning use the same config. No VLANs.In provisioning did you set the same configuration?
Are you using VLAN?
# mar/26/2023 18:19:39 by RouterOS 7.9beta4
# software id = BH9H-NUQS
#
# model = C53UiG+5HPaxD2HPaxD
# serial number = HDG08SFXXXX
/interface bridge
add admin-mac=48:A9:8A:0E:18:EB auto-mac=no comment=defconf name=bridge
/interface wifiwave2 channel
add band=5ghz-ax disabled=no frequency=5180-5500 name=36-100 \
skip-dfs-channels=10min-cac width=20/40/80mhz
add band=2ghz-ax disabled=no frequency=2412-2437 name=1-6 width=20/40mhz
/interface wifiwave2 security
add authentication-types=wpa2-psk disabled=no ft=yes ft-over-ds=yes \
management-protection=disabled name=SecWiFi-1 wps=disable
/interface wifiwave2 configuration
add channel=1-6 country=Italy disabled=no mode=ap name="2.4 GHz" security=\
SecWiFi-1 ssid=MikroTik
add channel=36-100 country=Italy disabled=no mode=ap name="5 GHz" security=\
SecWiFi-1 ssid=MikroTik
/interface wifiwave2
add channel.frequency=5180-5500 configuration="5 GHz" configuration.manager=\
local .mode=ap disabled=no name=cap-wifi1
add channel.frequency=2412-2437 configuration="2.4 GHz" \
configuration.manager=local .mode=ap disabled=no name=cap-wifi2
set [ find default-name=wifi1 ] channel.frequency=5180-5500 configuration=\
"5 GHz" configuration.manager=local .mode=ap disabled=no
set [ find default-name=wifi2 ] channel.frequency=2412-2437 configuration=\
"2.4 GHz" configuration.manager=local .mode=ap disabled=no
/interface bridge port
add bridge=bridge comment=defconf interface=ether2
add bridge=bridge comment=defconf interface=ether3
add bridge=bridge comment=defconf interface=ether4
add bridge=bridge comment=defconf interface=ether5
add bridge=bridge comment=defconf interface=wifi1
add bridge=bridge comment=defconf interface=wifi2
add bridge=bridge comment="minidlna container" interface=veth1
/ip neighbor discovery-settings
set discover-interface-list=LAN
/ipv6 settings
set max-neighbor-entries=15360
/interface list member
add comment=defconf interface=bridge list=LAN
add comment=defconf interface=ether1 list=WAN
add comment=FTTH interface=pppoe-out1 list=WAN
/interface wifiwave2 capsman
set enabled=yes interfaces=bridge package-path="" require-peer-certificate=no \
upgrade-policy=none
/interface wifiwave2 provisioning
add action=create-dynamic-enabled disabled=no master-configuration="5 GHz" \
radio-mac=00:00:00:00:00:00 slave-configurations="2.4 GHz"
# mar/26/2023 18:20:41 by RouterOS 7.9beta4
# software id = R6XF-AV13
#
# model = C52iG-5HaxD2HaxD
# serial number = HE108MXXXXX
/interface bridge
add admin-mac=48:A9:8A:39:34:A4 auto-mac=no comment=defconf name=bridge
/interface wifiwave2
# managed by CAPsMAN
# mode: AP, SSID: MikroTik, channel: 5500/ax/Ceee
set [ find default-name=wifi1 ] configuration.manager=capsman .mode=ap \
disabled=no
# managed by CAPsMAN
# mode: AP, SSID: MikroTik, channel: 2417/ax/Ce
set [ find default-name=wifi2 ] configuration.manager=capsman .mode=ap \
disabled=no
/interface bridge port
add bridge=bridge comment=defconf interface=ether2
add bridge=bridge comment=defconf interface=ether3
add bridge=bridge comment=defconf interface=ether4
add bridge=bridge comment=defconf interface=ether5
add bridge=bridge comment=defconf interface=wifi1
add bridge=bridge comment=defconf interface=wifi2
add bridge=bridge comment=defconf interface=ether1
/ip neighbor discovery-settings
set discover-interface-list=LAN
/interface list member
add comment=defconf interface=bridge list=LAN
/interface wifiwave2 cap
set certificate=none discovery-interfaces=bridge enabled=yes
/ip dhcp-client
add comment=defconf interface=bridge
/ip dns
set allow-remote-requests=yes
It works because the remote caps, in the device with capsman manager enabled, are like local interfaces.If this is the case then I don't see how 802.11r can work between two capsman controlled APs and the local radio on your hAPax3.
You remember correctly, with OpenWrt it was exactly like this.I initially thought of WPA2/WPA3 causing issues (if I remember correctly, OpenWRT recommends using WPA2 with FT, for optimal roaming)
This also happened to me because I have misconfigured the bridges.phone is close to slave unit, still connected to main unit with a very low signal (lower than -75/-70) with no intention to connect to CAP no matter how long it stays there / both Android or iOS device manifest the same behaviour.
Spammers are continuing to bulls–t us...If you go to our documentation:
https://help.mikrotik.com/docs/display/ROS/WifiWave2
XX:XX:XX:XX:XX:XX@cap-wifi2 rejected, FT: FTE indicated that STA uses RSNXE, but RSNXE was not included
Happened to me too a while ago with an iPad, I was activating and deactivating the FT for testing.An iphone device generates this error in the logs, when in area of CAP.
Any particular (lack of) setting in the FT area that causes this?Code: Select allXX:XX:XX:XX:XX:XX@cap-wifi2 rejected, FT: FTE indicated that STA uses RSNXE, but RSNXE was not included
I don't think so, I've always used it in this way and never had a problem. FT is deactivated in the configuration, it is only active in the security profile, and that's how it should work... if I specify a security profile the profile settings are used.the issue came from using security profiles defined in the "security" tab and assigned within the profiles defined in "configuration".
Yep, it's good that it worksI recently also did the same setup with two hAP ax2 and FT works great.
I don't know if it's a specific Audience issue...
However the important thing is that it works
One the family phones is a Huawei (P40 Pro) and has the same issue - won't change for nothing, not even from 5GHz to 2.4GHz, not to mention from main to cap... My Huawei pad can see FT enable but doesn't want to roam from 2.4GHz to 5GHz ...
it's in 7.11rc2Hi
After watching Andrews brilliant presentation : https://www.youtube.com/watch?v=4Ua2lI6HBhE&t=1374s
I'd like to know how to disable 802.11v (wnm)
It's clearly mentioned on the WW2 page : https://bit.ly/3KxvbQe
But I don't see how to reach it under RouterOS ?
interface/wifiwave2/steering/neighbor-group/print