Your message dated Mon, 4 Sep 2023 12:48:14 +0200
with message-id <[email protected]>
and subject line Re: Bug#1051086: general: networking misconfigured and
unusable after bookworm upgrade
has caused the Debian Bug report #1051086,
regarding general: networking misconfigured and unusable after bookworm upgrade
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
1051086: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051086
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
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.
--- End Message ---
--- Begin Message ---
On Sun, 3 Sep 2023 11:17:02 -0600 "D. R. Evans" <[email protected]> wrote:
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)
http://enginehousebooks.com/drevans
Thanks for the additional information.
This confirms, that the connection configuration you have is not bound
to a specific interface and NM will apply it to any interface.
In your case, you want to bind it to a specific interface though, so you
need to set the "interface-name" option
See the corresponding man page nm-settings:
connection.interface-name
Alias: ifname
The name of the network interface this connection is bound to. If
not set, then the connection can be attached to any interface of the
appropriate type (subject to restrictions imposed by other settings).
For software devices this specifies the name of the created device.
For connection types where interface names cannot easily be made
persistent (e.g. mobile broadband or USB Ethernet), this property should not be
used. Setting this property restricts the interfaces a connection can be used
with, and if interface
names change or are reordered the connection may be applied to the
wrong interface.
You can easily set this property e.g. via nm-connection-editor.
In any case, this is not a bug in NetworkManager. It just worked by
accident for you. You have to keep in mind, that the kernel probes its
hardware asynchronously. So if the timing in the kernel changes, it can
influence the order in which the interfaces show up.
Closing the bug report.
Regards,
Michael
OpenPGP_signature.asc
Description: OpenPGP digital signature
--- End Message ---
_______________________________________________
Pkg-utopia-maintainers mailing list
[email protected]
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-utopia-maintainers
