Comment 4 for bug 2033099

I ran the exact command line the error report asked for when I entered the bug on the website. That's only 2 lines, I know. I'm sorry, but this is what the web page asks for. ubuntu-bug refused to work because it thinks it has no internet connection.

I'm aware of what a bug is. I'm a software developer, among other things.

The stuff on the support sites I've already looked at. No Joy.

Consider the software updater. It first fetches the package metadata from Internet. It then shows me the packages that need updating, but refuses to show me the package details (what was fixed etc) claiming it has no network connection. Then it goes on to update those very packages from the Internet. In my book that counts as a bug. Because it's not limited to just the software updater I chose to report the general issue rather than a software updater bug.

As for my system, it was installed from Unbuntu 20.04 desktop in 2021, an ISO downloaded from the Ubuntu site. I upgraded it to 22.04 using do-release-upgrade. Additions are chrome, opera, graphics drivers, libre office from libre office PPA, mysql repository (for the workbench only), nextcloud client, remmina from remmina, teams previes, and yubbico repository.

The problem has been there from the start, but I have not gotten round to reporting it earlier.

The machine is an AMD Ryzen 9 5950X with 128GB DDR4-3600 CL16, an Asus RTX4090 and a Samsung EVO 970 2TB as SSD. The MB is an MSI MPG Edge WiFi.

The connection is an ethernet connection, not WiFi.

I've checked the network traffic, there are no failed connections in a period where the issue shows itself. The firewall has two rules outgoing for this segment:

all->all any->25/tcp reject
all->all any->any allow

I doubt SMTP is used for connection checking and I see no connection attempts on 25/tcp
If I boot my machine in Windows, no issue. I'm aware Windows has a different mechanism for connection checking
If I connect the machine through my phone (5G) with a USB ethernet dongle on the phone the problem persists

I've thoroughly ruled out connectivity as the issue.

It may have something to with the fact that I use ifupdown for network configuration. When I first installed the machine netplan did not yet support all that I need in my network config. The ubuntu help site recommended falling back to ifupdown in that situation, so I did. I was unable to get NetworkManager running as needed either. But as ifupdown is formally supported by Ubuntu, other components should be able to work with it properly.