RE: dhcpcd kills all connections on Wi-Fi roaming betweenaccesspoints
Boris KrasnovskiyFri Dec 25 01:19:38 2020
➢ For the roaming test, my Asus RT-AC68 router and both 2.4 and 5 GHz bands enabled, and with different names (foobar and foobarX)
You cannot have different names, and test roaming names must be the same. If names are different Network considered to be different. Roaming is transitioning between access points with the same name. So to do roaming test you have to name both 2.4G and 5G networks the same: “foobar“. The reason people name 2.4G and 5G networks different is to prevent roaming.
From: bls s
Sent: Thursday, December 24, 2020 7:23 PM
To: Roy Marples; Boris Krasnovskiy
Subject: RE: dhcpcd kills all connections on Wi-Fi roaming betweenaccesspoints
Wasn't able to run all tests. Can't easily test roaming without household network wars, and don't have multiple nameservers.
Resolvconf -i results:
Wlan0 only: wlan0.dhcp (attached t-wifionly.txt)
Wlan0+eth0, no metrics set: eth0.dhcp wlan0.dhcp (attached t-wifiandether.txt)
Wlan0+eth0, lower wlan0 metric: wlan0.dhcp eth0.dhcp (attached t-wifiandetherwifiwins.txt)
I did notice one error in the dhcpcd output stream: ipv6_addaddr1: Permission denied
For the roaming test, my Asus RT-AC68 router and both 2.4 and 5 GHz bands enabled, and with different names (foobar and foobarX). But when I try to connect to the 5Ghz network for some reason it falls back to the 2.4. I don't understand how it even found the 2.4 SSID, they are different. The only way I can test roaming is to start with 5GHz, and then disable it (safe to do since nobody in the house uses it). But no joy.
From: Roy Marples <roy@xxxxxxxxxxxx>
Sent: Wednesday, December 23, 2020 7:18 PM
To: bls s <bls3427@xxxxxxxxxxx>; Boris Krasnovskiy <borkra@xxxxxxxxx>
Subject: Re: dhcpcd kills all connections on Wi-Fi roaming betweenaccesspoints
On 24/12/2020 01:46, bls s wrote:
> My duh. Started it from the command line and seems to be working correctly.
> Previously it failed immediately, this has gone through 5 renewals with no problem.
Great, but we should be testing wireless roaming keeping the DNS yes?
Ideally test with an ethernet cable attached as well.
Set the metric of the wireless interface lower than the wired interface in dhcpcd.conf
`resolvconf -i` should list the wireless over the ethernet
Let the wireless roam and they should swap.
dhcpcd will do the same as well without resolvconf, but you would need to ensure both interfaces used a different nameserver and then inspect /etc/resolv.conf to ensure they swapped.
Let the wireless connect and they should swap again.
Let me know how it works out.
Archive administrator: firstname.lastname@example.org