Re: bookworm and network connections

["D. R. Evans" <doc.evans@gmail.com>]

Thank you for your thoughts...

As people are addressing the rc.local issue (I now realise that I shouldn't 
have mentioned it :-) )... I just checked, and:

1. rc.local is being executed;
2. it is executing the nmcli commands;
3. the commands are successful.

But it remains true that when the boot is fully complete, the networking is 
still hosed in the way that I described. So, apparently, putting commands in 
rc.local doesn't provide the workaround that I expected. I think that we 
should concentrate on the underlying networking issue so that it comes up 
properly rather than being derailed by trying to fix the networking after the 
fact.

[[ I speculate wildly that systemd or something doesn't complete configuring 
the network until after rc.local has finished processing (I know that rc.local 
executes late in the boot process, but I don't think that that means that 
everything else has *finished* executing when rc.local runs). I may easily be 
wrong, but really I don't think I care. ]]

I just want to get the networking to come up properly :-)

I don't understand modern systemd-controlled networking initiation well enough 
to know where to look for something that the upgrade might have clobbered, nor 
how I might go about fixing it.

  Doc

--
Web:  http://enginehousebooks.com/drevans