Re: on switching back and forth between access points

On 8/14/26 02:54, Lawrence D’Oliveiro wrote:
> On Tue, 11 Aug 2026 13:06:20 -0300, Anton Antimo wrote:
> 
>> Is this really usual? This is small cafeteria---some 25 square
>> meters---and it switches me from access point dc:2c:6e:c4:1e:a9 to
>> dc:2c:6e:c4:1e:a8 every now and then. I also began to see these
>> missed-beacon messages, which I don't know what they mean. (Any
>> explanation would be appreciated.)
> 
> Just my guess, but Linux daemons are known to be pretty chatty in
> their log messages. Besides which, remember a lot of consumer
> hardware, including wi-fi hardware, is expected to be sold pretty much
> exclusively to Windows users. (“Linux? What’s that?”)
> 
> What this means is, the vendors who make this stuff often don’t do
> proper standards-compliance testing, their attitude is “if it seems to
> work OK with Windows, ship it”. So then the Linux developers find
> shortcomings, and have to work around them in open-source drivers.
> 
> Combine the two facts, and you’re going to see lots of complaints in
> your logs about issues that neither you nor the driver developers are
> in a position to fix.
> 
>> [Aug11 11:27] iwlwifi 0000:00:14.3: missed beacons exceeds threshold, but receiving data. Stay connected, Expect bugs.
> 
> If you don’t notice any actual disruptions to network connections, I
> would conclude that this is normal ;).

   Ummm ... I implemented a 'roving' net detection
   thing ON A PI3 used as the 4th-tier backup device.
   Had a USB laptop-sized mag drive attached with a
   rubber band, did the 'most important' backups of
   the backups daily.

   However there were three APs kind of in range.
   DID find some tweaks to get the built-in software
   to check/switch to the BEST one in a fairly
   dynamic fashion. "Does work regardless" was the
   goal, not necessarily speed. Will have to dig thru
   some of my old office shit ... would have documented
   it somewhere. Used the 'usual' older net utilities
   though, not anything exotic, no extra coding.

   As for the OP ... maybe the defaults, and power of
   the APs, make the algo too twitchy ? Some plain old
   'static' network defs can force it to use just ONE
   however.

   Anyway, try starting here :
   https://linuxvox.com/blog/connect-automatically-with-priority-linux/