Re: Wifi error log for Bookworm?

On 31/10/2024 09:46, The Natural Philosopher wrote:

On 30/10/2024 21:24, druck wrote:

On 29/10/2024 21:08, Lawrence D'Oliveiro wrote:

On Tue, 29 Oct 2024 20:28:40 +0000, druck wrote:
>

Quite often my Linux Laptops which use Network Manager decide
they would like to try WiFi networks other than the one I've chosen,
that's easily fixed via the gui, but not what you want on headless
systems.

>
You could use nmcli to control it.

>
If you can log in to a headless system which isn't connecting to the Wifi.
>

Well at least all headless Pis will run a console session via some form of USB keyboard and HDMI screen. You wont need a mouse so one USB port is enough
 That what I have used when faced with loss of of connectivity.

Yes, I'm sure I could drag a monitor and keyboard up to the attic, or down to the shed. However, it's easier in most situations to bring the Pi back to the monitor and keyboard to sort it out.
But the point is; with the previous DHCPCD/WPAsuplicant the selection of the WiFi network was immutable. With the hardware watchdog set to reboot on crashes, if you couldn't connect to the Pi it was more likely the AP wasn't working.
However, when using Network Manager, it sometimes decides to try a different network, leaving a remote headless Pi stuffed. Whilst all my 'desktop/media' Pi's (connected to monitors and keyboards) are on Bookworm, all the headless ones are remaining on Bullseye for the time being.
---druck