No outbound network access after Ubuntu 22.04LTS update

Ubuntu Version: Ubuntu 22.04.5 LTS, but the machine is dual-boot with Win 11.

Desktop Environment (if applicable): both GNOME and KDE installed, mostly run GNOME.

Problem Description:
After updating on 12/11/2025, outgoing networking has stopped working:

  • web browsing times out regardless of URL
  • all pings fail with 100% packet loss
  • outgoing SSH times out regardless of destination
  • after a hard reboot and connection to the network, the system clock is set ~8hr early even though the BIOS clock is correct. The time difference is not an even number of hours.
  • on the same day, before the update, network access was normal.

However, inbound SSH connections succeed.
Pinging the machine from another machine on the network evokes no response.

Network Manager claims the machine is connected (via wired ethernet).
There are two network adapters, but only the one connected to the WAN is on.

A Dell laptop with the same similar configuration fails identically.

I’d be grateful for any insight into this problem.

What I’ve tried so far:
Disabling the firewall (ufw) has no effect.
Hard rebooting the machine does not resolve the problem.
Disabling apparmor has no effect, and there are no apparmor denials in the kernel log.
Everything is functional after booting the machine into Win 11, so there are no hardware or cabling issues.
Booting from an earlier kernel (6.8.0-87) does not resolve the problem.

The machine is configured to NASA CSET operating system standards and uses PKCS11 smart card for log-in and authentication.

The apt history for 12/11 is as follows:
Start-Date: 2025-12-11 08:26:59 -------------------------------------------------------------------
Commandline: packagekit role=‘update-packages’
Requested-By: ehildum (1000)
Install:
linux-hwe-6.8-headers-6.8.0-88:amd64 (6.8.0-88.89~22.04.2, automatic),
linux-hwe-6.8-tools-6.8.0-88:amd64 (6.8.0-88.89~22.04.2, automatic),
linux-tools-6.8.0-88-generic:amd64 (6.8.0-88.89~22.04.2, automatic),
linux-modules-extra-6.8.0-88-generic:amd64 (6.8.0-88.89~22.04.2, automatic),
linux-headers-6.8.0-88-generic:amd64 (6.8.0-88.89~22.04.2, automatic),
linux-modules-6.8.0-88-generic:amd64 (6.8.0-88.89~22.04.2, automatic),
linux-image-6.8.0-88-generic:amd64 (6.8.0-88.89~22.04.2, automatic)

Upgrade:
python3-apparmor:amd64 (3.0.4-2ubuntu2.4, 3.0.4-2ubuntu2.5),
linux-tools-common:amd64 (5.15.0-163.173, 5.15.0-164.174),
udev:amd64 (249.11-0ubuntu3.16, 249.11-0ubuntu3.17),
systemd-oomd:amd64 (249.11-0ubuntu3.16, 249.11-0ubuntu3.17),
systemd-container:amd64 (249.11-0ubuntu3.16, 249.11-0ubuntu3.17),
google-chrome-stable:amd64 (143.0.7499.40-1, 143.0.7499.109-1),
systemd-timesyncd:amd64 (249.11-0ubuntu3.16, 249.11-0ubuntu3.17),
libpam-systemd:amd64 (249.11-0ubuntu3.16, 249.11-0ubuntu3.17),
ubuntu-drivers-common:amd64 (1:0.9.6.2~0.22.04.8, 1:0.9.6.2~0.22.04.9),
apparmor:amd64 (3.0.4-2ubuntu2.4, 3.0.4-2ubuntu2.5),
linux-generic-hwe-20.04:amd64 (5.15.0.163.158, 5.15.0.164.159),
linux-image-generic-hwe-22.04:amd64 (6.8.0-87.88~22.04.1, 6.8.0-88.89~22.04.2),
libsystemd0:amd64 (249.11-0ubuntu3.16, 249.11-0ubuntu3.17),
libsystemd0:i386 (249.11-0ubuntu3.16, 249.11-0ubuntu3.17),
libnss-systemd:amd64 (249.11-0ubuntu3.16, 249.11-0ubuntu3.17),
libapparmor1:amd64 (3.0.4-2ubuntu2.4, 3.0.4-2ubuntu2.5),
libapparmor1:i386 (3.0.4-2ubuntu2.4, 3.0.4-2ubuntu2.5),
ioninja:amd64 (5.9.0, 5.9.1),
apparmor-utils:amd64 (3.0.4-2ubuntu2.4, 3.0.4-2ubuntu2.5),
systemd:amd64 (249.11-0ubuntu3.16, 249.11-0ubuntu3.17),
libudev1:amd64 (249.11-0ubuntu3.16, 249.11-0ubuntu3.17),
libudev1:i386 (249.11-0ubuntu3.16, 249.11-0ubuntu3.17),
python3-attr:amd64 (21.2.0-1, 21.2.0-1ubuntu1),
libnss-mymachines:amd64 (249.11-0ubuntu3.16, 249.11-0ubuntu3.17),
linux-headers-generic-hwe-22.04:amd64 (6.8.0-87.88~22.04.1, 6.8.0-88.89~22.04.2),
linux-generic-hwe-22.04:amd64 (6.8.0-87.88~22.04.1, 6.8.0-88.89~22.04.2),
python3-libapparmor:amd64 (3.0.4-2ubuntu2.4, 3.0.4-2ubuntu2.5),
systemd-sysv:amd64 (249.11-0ubuntu3.16, 249.11-0ubuntu3.17),
linux-libc-dev:amd64 (5.15.0-163.173, 5.15.0-164.174),
linux-libc-dev:i386 (5.15.0-163.173, 5.15.0-164.174)

End-Date: 2025-12-11 08:29:05

Further information from various utilities is as follows:
ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: enp3s0f0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000
link/ether 98:b7:85:00:10:8c brd ff:ff:ff:ff:ff:ff
3: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
link/ether 00:4e:01:9d:0a:8f brd ff:ff:ff:ff:ff:ff
altname enp0s31f6
inet 10.235.9.4/19 brd 10.235.31.255 scope global dynamic noprefixroute eno1
valid_lft 2590147sec preferred_lft 2590147sec
inet6 fe80::ec9:5e52:f24c:5a42/64 scope link noprefixroute
valid_lft forever preferred_lft forever
4: enp3s0f1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
link/ether 98:b7:85:00:10:8d brd ff:ff:ff:ff:ff:ff
5: virbr0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default qlen 1000
link/ether 52:54:00:22:94:d6 brd ff:ff:ff:ff:ff:ff
inet 192.168.122.1/24 brd 192.168.122.255 scope global virbr0
valid_lft forever preferred_lft forever

ip route show
default via 10.235.0.1 dev eno1 proto dhcp metric 20101
10.235.0.0/19 dev eno1 proto kernel scope link src 10.235.9.4 metric 101
169.254.0.0/16 dev virbr0 scope link metric 1000 linkdown
192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 linkdown

resolvectl status
Global
Protocols: -LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported
resolv.conf mode: stub

Link 2 (enp3s0f0)
Current Scopes: none
Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported

Link 3 (eno1)
Current Scopes: DNS
Protocols: +DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported
Current DNS Server: 143.232.252.34
DNS Servers: 143.232.252.34 128.102.0.34 128.102.254.34
DNS Domain: ndc.nasa.gov

Link 4 (enp3s0f1)
Current Scopes: none
Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported

Link 5 (virbr0)
Current Scopes: none
Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported

ping 10.235.0.1
PING 10.235.0.1 (10.235.0.1) 56(84) bytes of data.
^C
— 10.235.0.1 ping statistics —
35 packets transmitted, 0 received, 100% packet loss, time 34796ms

cat /etc/resolv.conf

This is /run/systemd/resolve/stub-resolv.conf managed by man:systemd-resolved(8).

Do not edit.

This file might be symlinked as /etc/resolv.conf. If you’re looking at

/etc/resolv.conf and seeing this text, you have followed the symlink.

This is a dynamic resolv.conf file for connecting local clients to the

internal DNS stub resolver of systemd-resolved. This file lists all

configured search domains.

Run “resolvectl status” to see details about the uplink DNS servers

currently in use.

Third party programs should typically not access this file directly, but only

through the symlink at /etc/resolv.conf. To manage man:resolv.conf(5) in a

different way, replace this symlink by a static file or a different symlink.

See man:systemd-resolved.service(8) for details about the supported modes of

operation for /etc/resolv.conf.

nameserver 127.0.0.53
options edns0 trust-ad
search ndc.nasa.gov

ping -c 4 8.8.8.8
PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.

— 8.8.8.8 ping statistics —
4 packets transmitted, 0 received, 100% packet loss, time 3099ms

cat /etc/netplan/*.yaml

Let NetworkManager manage all devices on this system

network:
version: 2
renderer: NetworkManager

ufw status verbose
Status: active
Logging: on (low)
Default: deny (incoming), allow (outgoing), deny (routed)
New profiles: skip

To Action From


22/tcp ALLOW IN Anywhere
497/tcp ALLOW IN Anywhere
497/udp ALLOW IN Anywhere
2048,3128,3130,3401,4827/tcp (Squid) ALLOW IN Anywhere
3128 ALLOW IN Anywhere
1022/tcp ALLOW IN Anywhere
22/tcp (v6) ALLOW IN Anywhere (v6)
497/tcp (v6) ALLOW IN Anywhere (v6)
497/udp (v6) ALLOW IN Anywhere (v6)
2048,3128,3130,3401,4827/tcp (Squid (v6)) ALLOW IN Anywhere (v6)
3128 (v6) ALLOW IN Anywhere (v6)
1022/tcp (v6) ALLOW IN Anywhere (v6)

Many thanks,
Ted Hildum

This appears to be a driver problem. Connecting through a USB - Ethernet dongle brings back normal network access.

Reverting ubuntu-drivers-common from the new 1:0.9.6.2~0.22.04.9 back to 1:0.9.6.2~0.22.04.8 did not fix the problem. Not too surprising since there don’t appear to be network drivers in the package. I expect the network drivers to be in the kernel packages, but booting from the 6.8.0-87 kernel did not fix the problem either.

EAH

This topic was automatically closed after 30 days. New replies are no longer allowed.