Package: general
Severity: important
Dear Maintainer,
* What led up to the situation?
Upgrade from bullseye to bookworm. Everything worked before the upgrade.
* What exactly did you do (or not do) that was effective (or
ineffective)?
Details of the original problem may be found at:
https://lists.debian.org/debian-user/2023/09/msg00024.html
Extracting from that post:
++++
When I booted the machine after the upgrade [from bullseye to bookworm], no
networking was working at all, on either interface, even though:
----
zserver# nmcli networking connectivity
full
zserver#
----
which was definitely a lie, as nothing was successfully going in or out of the
machine.
Looking in more detail:
----
[Z:~] nmcli
enp12s0: connected to Wired connection enp11s0(eth0)
"Intel I210"
ethernet (igb), D8:50:E6:C2:76:03, hw, mtu 1500
ip4 default
inet4 209.97.232.18/24
route4 209.97.232.0/24 metric 100
route4 default via 209.97.232.1 metric 100
inet6 fe80::e0c1:20a:c535:873c/64
route6 fe80::/64 metric 1024
lo: connected (externally) to lo
"lo"
loopback (unknown), 00:00:00:00:00:00, sw, mtu 65536
inet4 127.0.0.1/8
inet6 ::1/128
enp11s0: disconnected
"Intel I210"
1 connection available
ethernet (igb), D8:50:E6:C2:76:02, hw, mtu 1500
enp13s0: unavailable
"Intel I210"
ethernet (igb), D8:50:E6:C2:76:04, hw, mtu 1500
enp14s0: unavailable
"Intel I210"
ethernet (igb), D8:50:E6:C2:76:05, hw, mtu 1500
DNS configuration:
servers: 127.0.0.1 209.97.224.2 209.97.224.3
interface: enp12s0
----
Somehow, it had got into a state where enp12s0 was connected to enp11s0
(whatever that means), with the result that nothing worked.
So, after a bit of messing around with an increasing sense of desperation, I
discovered that:
----
[Z:~] sudo nmcli connection down "Wired connection enp11s0(eth0)"
Connection 'Wired connection enp11s0(eth0)' successfully deactivated (D-Bus
active path: /org/freedesktop/NetworkManager/ActiveConnection/2)
[Z:~] sudo nmcli connection up "Wired connection enp11s0(eth0)"
Connection successfully activated (D-Bus active path:
/org/freedesktop/NetworkManager/ActiveConnection/4)
----
resulted in:
----
[Z:~] nmcli
enp11s0: connected to Wired connection enp11s0(eth0)
"Intel I210"
ethernet (igb), D8:50:E6:C2:76:02, hw, mtu 1500
ip4 default
inet4 209.97.232.18/24
route4 209.97.232.0/24 metric 101
route4 default via 209.97.232.1 metric 101
inet6 fe80::1ae1:dfcf:be36:f72f/64
route6 fe80::/64 metric 1024
enp12s0: connected to Wired connection enp12s0(eth1)
"Intel I210"
ethernet (igb), D8:50:E6:C2:76:03, hw, mtu 1500
inet4 192.168.0.1/24
route4 192.168.0.0/24 metric 100
inet6 fe80::d30e:86f6:ca86:8986/64
route6 fe80::/64 metric 1024
lo: connected (externally) to lo
"lo"
loopback (unknown), 00:00:00:00:00:00, sw, mtu 65536
inet4 127.0.0.1/8
inet6 ::1/128
enp13s0: unavailable
"Intel I210"
ethernet (igb), D8:50:E6:C2:76:04, hw, mtu 1500
enp14s0: unavailable
"Intel I210"
ethernet (igb), D8:50:E6:C2:76:05, hw, mtu 1500
DNS configuration:
servers: 127.0.0.1 209.97.224.2 209.97.224.3
interface: enp11s0
----
and indeed, everything was now working.
++++
Skipping a bunch of stuff in the thread that started at
https://lists.debian.org/debian-user/2023/09/msg00024.html, I eventually found
that adding the lines:
----
nmcli connection down "Wired connection enp11s0(eth0)"
nmcli connection up "Wired connection enp11s0(eth0)"
----
did NOT fix the problem, even though when I entered those same commands
manually post-boot, the network did begin to function properly. (That is, when
I put those line in rc.local, then enp12s0 was still connected to enp11s0 at
the end of the boot process.)
After considerable experimentation I found that the result was unchanged if I
tried:
----
nmcli connection down "Wired connection enp11s0(eth0)"
sleep 10
nmcli connection up "Wired connection enp11s0(eth0)"
----
BUT, if I changed the sleep time to 20:
nmcli connection down "Wired connection enp11s0(eth0)"
sleep 20
nmcli connection up "Wired connection enp11s0(eth0)"
----
networking was function correctly post-boot.
This is all completely reproducible here.
* What was the outcome of this action?
Without changing the networking either in rc.local (with a considerable delay
between the commands) or manually folllowing compleion of the boot process,
networking does not work. In particular nmcli says:
----
enp12s0: connected to Wired connection enp11s0(eth0) <------ this seems really
weird
"Intel I210"
ethernet (igb), D8:50:E6:C2:76:03, hw, mtu 1500
ip4 default
inet4 209.97.232.18/24
route4 209.97.232.0/24 metric 100
route4 default via 209.97.232.1 metric 100
inet6 fe80::e0c1:20a:c535:873c/64
route6 fe80::/64 metric 1024
enp11s0: disconnected
"Intel I210"
1 connection available
ethernet (igb), D8:50:E6:C2:76:02, hw, mtu 1500
----
and no networking works.
* What outcome did you expect instead?
I expected networking to function correctly, as it did in (at least) stretch,
buster and bullseye.
I checked, and the upgrade made no change to the networking configuration files
in /etc/NetworkManager except for the addition of a file "ntpsec" in
/etc/NetworkManager/dispatcher.d.
