Path: ...!eternal-september.org!feeder2.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: druck <news@druck.org.uk>
Newsgroups: comp.sys.raspberry-pi
Subject: Re: Wifi error log for Bookworm?
Date: Thu, 31 Oct 2024 21:54:40 +0000
Organization: A noiseless patient Spider
Lines: 38
Message-ID: <vg0ub0$2rtar$1@dont-email.me>
References: <vff1oh$30ljh$1@dont-email.me>
 <KOudndzl6uD98oD6nZ2dnZfqn_SdnZ2d@giganews.com> <vflpm5$gigb$1@dont-email.me>
 <vfm4ov$ifnc$1@dont-email.me> <vfo90b$11gf5$3@dont-email.me>
 <vfohs7$13j16$1@dont-email.me> <vfomlo$14f3e$1@dont-email.me>
 <vfrgho$1mkm5$1@dont-email.me> <vfrisv$1n56m$6@dont-email.me>
 <vfu85s$2ad65$3@dont-email.me> <vfvjmf$2khfc$7@dont-email.me>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Injection-Date: Thu, 31 Oct 2024 22:54:41 +0100 (CET)
Injection-Info: dont-email.me; posting-host="1b5608d2dbba4a6a43637f36b1ccd14e";
	logging-data="3011931"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX18qyQMgd1yP6hr93oYjA8lf"
User-Agent: Mozilla Thunderbird
Cancel-Lock: sha1:AY+Z4++Ni3j8V62OQcmREGC/S+g=
In-Reply-To: <vfvjmf$2khfc$7@dont-email.me>
Content-Language: en-GB
Bytes: 2857

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