RE: dhcpcd kills all connections on Wi-Fi roaming betweenaccesspoints
Boris KrasnovskiyFri Dec 25 01:23:29 2020
The problem, vanished I cannot duplicate it any more. So I guess all is working until I can figure out the condition that broke this.
From: Roy Marples
Sent: Thursday, December 24, 2020 3:38 AM
To: Boris Krasnovskiy
Cc: bls s; dhcpcd-discuss@xxxxxxxxxxxx
Subject: Re: dhcpcd kills all connections on Wi-Fi roaming betweenaccesspoints
On 24/12/2020 06:42, Boris Krasnovskiy wrote:
> Hi Roy,
> > In previous emails you've indicated that in the roaming state it never actually
> > goes down, just back up again which could take time to find an AP. As such,
> > you'll have a hard job convincing me that the working ethernet you just plugged
> > into should not take precedence by default.
> If Ethernet would always take precedence it would be ok, but that was not what
> Before roaming Wi-FI took precedence after Ethernet.
I'm not sure I fully understand.
With the the default metrics (see below), ethernet will always take precedence
over wifi all other things being equal. Wireless gets boosted to a higher metric.
Could you describe the DNS result at each step and expectations?
That might help.
> In the particular test, I did not have ‘-m’ set, not sure what are the defaults.
> Yes, using route metric, if non set on the command line is ok.
OK, lets keep to using the defaults.
To be clear, are you using any resolvconf and does it have the -C/-c options?
> But if metric specified on the dhcpcd command line it should be used.
Job for another day.
Archive administrator: firstname.lastname@example.org