Hello
On my OpenWrt router I have two SSIDs with the same name, one is with a frequency of 5GHz and the second with a frequency of 2.4GHz.
Is it possible to change the channel automatically when you get closer (5GHz) and when you move away ironing at 2.4GHz without disconnection?
It seems to me that currently my configuration does not allow it and if I get closer to my router, I stay in 2.4GHz and I have to reconnect to the SSID to go to 5GHz.
Thank you for your explanations
Install wpad-mbedtls in place of wpad-basic-mbedtls and use either usteer or dawn to steer clients.
For what it's worth, I have a similar setup: Two SSIDs, one on 2.4GHz and one on 5GHz, with the same name/password/encryption scheme (WPA3 SAE if that matters) out of the same router, a Netgear WAX206. Of course they're also both part of the br-lan interface.
Clients (Linux laptop, Pixel phone) seem to do the "right thing" automagically (in their WLAN adapter firmware or the OS WLAN client stack, haven't investigated):
2.4GHz to 5GHz: E.g. walking into the house with the phone, or the laptop connecting immediately after the router has been rebooted when the 5GHz AP isn't available yet (radio is set to use DFS channel so it's still doing its radar scan for 1 minute): Initially connecting on 2.4GHz, some time later (can be a small number of minutes) I find it on 5GHz.
5GHz to 2.4GHz: Walking just outside the house (or even just to the basement where the 5GHz signal is weak), the phone seems to quickly switch to the 2.4GHz SSID.
In both cases the clients keep the same IP addresses.
Using wpad-mbedtls but no usteer, dawn or any other fast roaming support.
The 5GHz radio is 80MHz wide ax (aka WiFi 6), whereas the 2.4GHz one is 20MHz n (aka WiFi 4). So the bandwidth is much higher on the 5GHz AP when in range. This probably plays a role in the client eventually "preferring" 5GHz when it's available.
Quick add for reference: Here's what the kernel log looks like on the Linux laptop waking up from suspend. xx:xx:xx:xx:xx:xx is the 2.4GHz AP MAC, and yy:yy:yy:yy:yy:yy is the 5GHz AP MAC. As shown in this example, when the client WLAN adapter is "warm" (some state seems to be kept through the s2idle suspend state), it hops on the 5GHz AP very quickly.
Feb 11 09:57:24 kernel: wlp1s0: authenticate with xx:xx:xx:xx:xx:xx (local address=nn:nn:nn:nn:nn:nn)
Feb 11 09:57:24 kernel: wlp1s0: send auth to xx:xx:xx:xx:xx:xx (try 1/3)
Feb 11 09:57:24 kernel: wlp1s0: authenticate with xx:xx:xx:xx:xx:xx (local address=nn:nn:nn:nn:nn:nn)
Feb 11 09:57:24 kernel: wlp1s0: send auth to xx:xx:xx:xx:xx:xx (try 1/3)
Feb 11 09:57:24 kernel: wlp1s0: authenticated
Feb 11 09:57:24 kernel: wlp1s0: associate with xx:xx:xx:xx:xx:xx (try 1/3)
Feb 11 09:57:24 kernel: wlp1s0: RX AssocResp from xx:xx:xx:xx:xx:xx (capab=0x431 status=0 aid=1)
Feb 11 09:57:24 kernel: wlp1s0: associated
Feb 11 09:57:35 kernel: wlp1s0: disconnect from AP xx:xx:xx:xx:xx:xx for new auth to yy:yy:yy:yy:yy:yy
Feb 11 09:57:35 kernel: wlp1s0: authenticate with yy:yy:yy:yy:yy:yy (local address=nn:nn:nn:nn:nn:nn)
Feb 11 09:57:35 kernel: wlp1s0: send auth to yy:yy:yy:yy:yy:yy (try 1/3)
Feb 11 09:57:35 kernel: wlp1s0: authenticate with yy:yy:yy:yy:yy:yy (local address=nn:nn:nn:nn:nn:nn)
Feb 11 09:57:35 kernel: wlp1s0: send auth to yy:yy:yy:yy:yy:yy (try 1/3)
Feb 11 09:57:35 kernel: wlp1s0: authenticated
Feb 11 09:57:35 kernel: wlp1s0: associate with yy:yy:yy:yy:yy:yy (try 1/3)
Feb 11 09:57:35 kernel: wlp1s0: RX ReassocResp from yy:yy:yy:yy:yy:yy (capab=0x111 status=0 aid=2)
Feb 11 09:57:35 kernel: wlp1s0: associated
Feb 11 09:57:36 kernel: wlp1s0: Limiting TX power to 21 (24 - 3) dBm as advertised by yy:yy:yy:yy:yy:yy