debcrafters-packages team mailing list archive

[Charles Marlow <2110517@xxxxxxxxxxxxxxxxxx>]

** Package changed: ubuntu => network-manager (Ubuntu)

-- 
You received this bug notification because you are a member of
Debcrafters packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/2110517

Title:
  Wired connection in bonded interface not disabled/enabled when cable
  unplugged/plugged-in

Status in network-manager package in Ubuntu:
  New

Bug description:
  network-manager/noble-updates,now 1.46.0-1ubuntu2.2 amd64
  netplan.io/noble-updates,now 1.1.2-2~ubuntu24.04.1 amd64

  Using the Network Manager GUI I created an Ethernet-WiFi active-backup
  bond.  To set the primary interface, I had to use the workaround
  described in Bug #2098093
  (https://bugs.launchpad.net/ubuntu/+source/network-
  manager/+bug/2098093).  Then, I used a script in
  /usr/lib/NetworkManager/dispatcher.d/ to make the Ethernet and WiFi
  mutually exclusive.

  When I unplugged the Ethernet cable, the wired connection was
  automatically disabled, the NetworkManager-dispatcher service ran the
  script, and my WiFi was enabled and connected.  When I plugged in the
  cable, the wired connection was automatically enabled, the script was
  run, and WiFi was disabled.  This was working since February until the
  past week or two, when I ran apt update/upgrade, which included a
  netplan.io upgrade from 1.1.1-1~ubuntu24.04.1 to
  1.1.2-2~ubuntu24.04.1.  I did not modify the bond settings, or any
  other network settings, in this time.

  Now, when I unplug the LAN, the wired connection is not automatically
  disabled, and the dispatcher script is not run.  Here is the complete
  output of journalctl --follow when I unplug the cable:

  May 13 01:27:54 Host kernel: e1000e 0000:00:19.0 enp0s25: NIC Link is Down
  May 13 01:27:54 Host kernel: bond0: (slave enp0s25): link status definitely down, disabling slave
  May 13 01:27:54 Host kernel: bond0: now running without any active interface!

  Nothing more happens, and the wired connection remains enabled.  If I
  manually disable the wired connection, then plug the cable back in, I
  get this from journalctl --follow:

  May 13 01:35:09 Host kernel: e1000e 0000:00:19.0 enp0s25: NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Txq
  May 13 01:35:09 Host NetworkManager[1572]: <info>  [1747114509.8554] device (enp0s25): carrier: link connected

  Nothing more is printed, and the wired connection remains disabled.  I
  have to manually enable the wired connection to get the
  NetworkManager-dispatcher to activate.

  This changed behaviour is *only* for my bonded interface.  If I use
  the Network Manager GUI to create a standard Ethernet Connection, and
  unplug the cable, I get:

  May 13 01:45:10 Host kernel: e1000e 0000:00:19.0 enp0s25: NIC Link is Down
  May 13 01:45:16 Host NetworkManager[1572]: <info>  [1747115116.5801] device (enp0s25): state change: activated -> unavailable (reason 'carrier-changed', sys-iface-state: 'managed')

  As expected, the non-bonded wired connection is automatically
  disabled, NetworkManager-dispatcher is activated, and my WiFi is
  enabled by the script (and I experience a brief moment of Linux Zen).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2110517/+subscriptions