INTL 3:770/1 3:770/3
REPLYADDR tnp@invalid.invalid
REPLYTO 3:770/3.0 UUCP
MSGID:  041ed1bf
REPLY:  85330ddc
PID: SoupGate-Win32 v1.05
On 31/10/2024 21:54, druck wrote:
> 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.

I already told you the solution to that.

There is a priority system in network manager.

Otherwise it will connect to whatever it connected to last time, or
sometimes not

If you have more than one connection profile use:

sudo nmcli c modify MYCONNECTIONNAME   connection.autoconnect-priority 1

Randomly created connections are default priority zero

This is also an accessible parameter from the GUI widget if you have a
GUI interface

It will then at least try only that SSID *first*

Or delete any alternative connection profiles.



--
    "Fanaticism consists in redoubling your effort when you have
forgotten your aim."

  George Santayana

--- SoupGate-Win32 v1.05
 * Origin: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3)
SEEN-BY: 19/38 90/1 105/81 106/201 128/187 129/305 153/757 7715 218/700
SEEN-BY: 218/840 220/70 226/17 30 100 227/114 229/110 111 114 200
SEEN-BY: 229/206 300 317 400 426 428 470 550 616 664 700 266/512 267/800
SEEN-BY: 282/1038 291/111 292/854 310/31 320/219 322/757 342/200 396/45
SEEN-BY: 460/58 633/280 281 412 418 420 509 2744 712/848 770/1 3 100
SEEN-BY: 770/330 340 772/210 220 230 5020/400 5075/35
PATH: 770/3 1 633/280 229/426