DHCP lease stop when roaming between AP

RouterOS Wireless Networking
1

Hi,

Im testing a L11UG-5HaxD to check the roaming capabilities in station mode with the qcom driver in comparison to a legacy wireless driver on a groove52hpn.

Im testing the equipment in a AGV, we configured the wifi interface in station mode and activated the 802.11r/k/v(FT/RRM/WNM), in fact we see the mikrotik does the fast roams correctly under 802.11r but we have a problem with the DHCP client.

The strategy is, local network in the eth1 and wan on the wifi1 which is the 5ghz iface, with masquerading we make the NATting, we set a DHCP client on wifi1 iface but every time the mkt roam between two AP the mkt itself release the ip lease and ask again when roam is completed.

/interface wifi configuration
add chains=0 channel.band=5ghz-ax .width=20/40mhz country=Spain disabled=no \
    installation=indoor mode=station name=cfg1 security.authentication-types=\
    wpa2-psk .encryption=ccmp .ft=yes .group-encryption=ccmp ssid="redacted" \
    station-roaming=yes steering.rrm=yes .wnm=yes tx-chains=0
/interface wifi
set [ find default-name=wifi1 ] configuration=cfg1 configuration.mode=station \
    disabled=no
/ipv6 settings
set disable-ipv6=yes
/ip address
add address=192.168.3.1/24 interface=ether1 network=192.168.3.0
/ip dhcp-client
add interface=wifi1
/ip firewall nat
add action=masquerade chain=srcnat out-interface=wifi1

image
image867×190 46.2 KB

Is any way to not lose the lease when the station roam between APs?

2

Just a guess, if you create a wan_bridge and add wifi1 to it and configure the dhcp client on wan_bridge, will the lease also be lost?

3

Hi safelogj, in fact we tested this and in fact it worked, but, at some point we lost remote connection to the mikrotik, and when we conected physically, the mkt was connected to the wifi, with a ip leased by the dhcp but it doesnt seem to communicate with the wan, we tried to renew it but it stucks at renewing an then rebind…, we had to disable and re-enable the wifi in order to work again.

I need to test more with the bridge and try to catch the issue with a packet capture in the bridge iface in order to diagnose more.

But anyway, as far as ai know, in the legacy wireless driver when the station roams doesnt lose the ip right?

4

sorry, I don't know. I just voiced my thought on how I would try to solve this. Perhaps I tried assigning the same MAC address to wan_bridge as wifi1.

5

"wifi" is not the legacy "wireless" driver...

6

Roaming isn't handled by a MikroTik device, or did I misunderstand?

7

-wireless is the legacy driver, in my case wifi-qcom is the “new“ driver
-Roaming IS handled by the mikrotik, i mean since the wifi iface is set to station and it roams between ap and FT is enabled it does, well both parties handle the FT since the 4-way handshake is ommited when 802.11r is working, in fact ia was able to check this by sniffing on another mkt device and capture the roam process on the target mkt

8

It's clear that the "station" is L11UG-5HaxD with wifi2 driver, that there are two device being compared inside one Automated Guided Vehicle, and one with the old driver (RBGroove52HPn, so not ac, not ax), is clear, but it's not AT ALL clear which these two access points are, what brand, what model, which ones are the controller of the other, or if is present a separate controller...

Did you write "roaming" or something else? If there aren't two access point involved, connected to each other that are actually roaming with each other, where does the roaming take place?