[Pkg-utopia-maintainers] Bug#1051086: general: networking misconfigured and unusable after bookworm upgrade

[D. R. Evans]

Michael Biebl wrote on 9/2/23 18:26:
> Control: reassign -1 network-manager
> 
> Am 02.09.23 um 16:51 schrieb D. R. Evans:
> 
>> [Z:~] nmcli
>> enp12s0: connected to Wired connection enp11s0(eth0)
> 
> It appears you have a connection configuration named "Wired connection
> enp11s0(eth0)" which is applied to enp12s0.
> This leads me to believe, that you don't have the connection
> configuration bound to a certain interface and as a result
> NetworkManager will pick the first one that is ready.

I don't know. The system set it all up in answer to my questions when debian 
stable was first installed on the machine, which I thinks was when debian 
stable was stretch; it has worked ever since then until the upgrade from 
bullseye to bookworm. Never really paid attention to any of this before, as it 
all worked fine; I'm just a user.

> 
> 
> You should be able to find the configuration file in
> /etc/NetworkManager/system-connections/ under the above name.
> 

There is a file called: "Wired connection enp11s0(eth0).nmconnection"

(The similar file for enp12s0 is, for some reason, called: "Wired connection 
enp12s0(eth1)"; i.e., no ".nmconnection" is part of its name)

> Please attach this file to the bug report.

Done. (At least, I'm attaching it to this e-mail and assuming that the 
software on the recipient machine is smart enough to extract it and add it to 
the report.)

Hmmmm... I see that the file for enp12s0 contains the line:
   mac-address=D8:50:E6:C2:76:03

whereas there is no similar line for enps11s0. Although one would think that 
the networking manager would be smart enough to figure out that if enps12s0 is 
on D8:50:E6:C2:76:03, then enp11s0 should be on the one other available active 
port. Maybe that used to be the case, but the current version of NM can no 
longer figure that out??? That could lead to something like what I'm seeing, I 
suppose. In which case, I suppose a wish request should be filed against NM to 
require it to behave intelligently in this case. It certainly seems that 
something has changed in NM such that a configuration that has worked 
correctly for a long time no longer does so.

-- 
Web:  http://enginehousebooks.com/drevans
-------------- next part --------------
[connection]
id=Wired connection enp11s0(eth0)
uuid=8e308949-5232-47aa-b9b6-8aab6369ec4d
type=ethernet
permissions=

[ethernet]
mac-address-blacklist=

[ipv4]
address1=209.97.232.18/24,209.97.232.1
dns=127.0.0.1;209.97.224.2;209.97.224.3;
dns-search=
method=manual

[ipv6]
addr-gen-mode=stable-privacy
dns-search=
method=auto

[proxy]