Thanks for the prompt response, I have attached the systemd / networkd logs that were requested. I have managed to repeating this issue on one machine, I might be able to get further logs from another machine that is on test.
This was the output of the tree command, there didn't seem to be anything in the Network Manager directory that was mentioned. /run/systemd/network/ └── 10-netplan-eno1.network 0 directories, 1 file ** Attachment added: "intel-bug.zip" https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/2115044/+attachment/5886231/+files/intel-bug.zip -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2115044 Title: Netplan and Intel e1000 Driver / I219-V Adapter Status in linux package in Ubuntu: New Status in netplan.io package in Ubuntu: Incomplete Bug description: Since the following change earlier in the year, I have been seeing issues with Intel's I219-V adapter. It's hard to say whether the problem is specifically Netplan or down to another change with the e1000 driver a month or so before. The main reason I am posting this here is because when machines were switched to Network Manager, the problem seemed to go away. (Replicated this work-around around with ~10 machines). https://changelogs.ubuntu.com/changelogs/pool/main/n/netplan.io/netplan.io_0.106.1-7ubuntu0.22.04.4/changelog * SECURITY REGRESSION: failure on systems without dbus - debian/netplan.io.postinst: Don't call the generator if no networkd configuration file exists. (LP: #2071333) I have had quite a few machines on our network loosing networking after a period of time. The organisation's network is software defined (Cisco) and uses 802.1x to authenticate machines to various sub-nets. Machines get an IP address at boot but loose connection after 3-6 hours. The syslog reports a constant stream of the following message. The Cisco logs seem to report "unable to obtain an IP address from DHCP". The machines seems to believe it still has the same IP address but is unable to communicate. [60689.477031] e1000e 0000:00:1f.6 enp0s31f6: Detected Hardware Unit Hang: TDH <13> TDT <15> next_to_use <15> next_to_clean <11> buffer_info[next_to_clean]: time_stamp <100e65bc0> next_to_watch <14> jiffies <100e65d58> next_to_watch.status <0> MAC Status <40080083> PHY Status <796d> PHY 1000BASE-T Status <3800> PHY Extended Status <3000> PCI Status <10> There is a similiar bug reported on the following post although this e1000e driver seems to have quite phases where it fails for people. It seemed that it's a long lived NIC installed over many years, there are quite a few firmware versions to support over it's lifetime. https://bugzilla.kernel.org/show_bug.cgi?id=118721 There was also a e1000e driver update via the Kernel package, this was around the same time range the Netplan changed. https://changelogs.ubuntu.com/changelogs/pool/main/l/linux- hwe-6.8/linux-hwe-6.8_6.8.0-60.63~22.04.1/changelog * Noble update: upstream stable patchset 2025-02-03 (LP: #2097301) - e1000e: change I219 (19) devices to ADP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2115044/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
