No ethernet connection in appVMs

Hi, I need some help with my internet connection. I’ve googled and read this forum but haven’t found the solution to my problem.

When I boot Qubes OS it gets connected to the internet via ethernet. Only ethernet, no Wi-Fi. The update manager automatically starts and templates are updated just fine. Then I start an appVM (any of my appVMs)… and internet connection problems appear. In a terminal I can ping google BUT the following gives no output:

$ curl -I

If I launch Firefox it doesn’t load any page:

Now I connect to my Wi-Fi network. In the terminal I can ping google AND the following works:

$ curl -I
HTTP/2 301 
content-type: text/html; charset=UTF-8
content-security-policy-report-only: object-src 'none';base-uri 'self';script-src 'nonce-LSOCLZBMvBu3Esrgh3ewkQ' 'strict-dynamic' 'report-sample' 'unsafe-eval' 'unsafe-inline' https: http:;report-uri
date: Tue, 12 Mar 2024 18:04:44 GMT
expires: Thu, 11 Apr 2024 18:04:44 GMT
cache-control: public, max-age=2592000
server: gws
content-length: 220
x-xss-protection: 0
x-frame-options: SAMEORIGIN
alt-svc: h3=":443"; ma=2592000,h3-29=":443"; ma=2592000

And Firefox works fine with the same page that previously failed:

One more thing. Now, if I disconnect from Wi-Fi, everything keeps working: ping, curl, web browser…, no internet connection problems at all.

I’m still new to Qubes. And I’m not a networking master so I would appreciate any help to fix this problem.

Is your wifi network on the same network as the ethernet one?

Did you create some firewall rules for sys-firewall?

Did you ping domain or ping (or some other IP address)?
Did you configure your ethernet connection manually or is it using DHCP?

Yes, both are in the same network. The network manager widget in the system tray gives me this information for both ethernet and wifi:

Broadcast address:
Subnet mask:
Default route:
Primary DNS:
Secondary DNS:
Tertiary DNS:

I’ve not created any rule for sys-firewall.

I ping If I ping to I get no output so it seems that there is a DNS problem, right?

My ethernet connection is using DHCP.

this looks weird for a DNS server, very unusual, did you set the value yourself?

are you using the same DNS server when connected with wifi?

1 Like

@solene I haven’t configured anything manually. As I said before both ethernet and wifi are using the same DNS servers.

I’ve just realized that, when I’m not connected via wifi, the command

$ curl -I

works in the qube sys-net but fails in sys-firewall.

In sys-net:

user@sys-net ~]$ cat /var/run/qubes/qubes-ns 
[user@sys-net ~]$ cat /etc/resolv.conf 
# Generated by NetworkManager

And in sys-firewall:

user@sys-firewall ~]$ cat /var/run/qubes/qubes-ns 
[user@sys-firewall ~]$ cat /etc/resolv.conf 

Seems to be the same issue:

Unusual yes - weird? I’ve seen it with ISPs and it’s part of a standard reserved
If eth0 is handing out that address I’d go back to whoever is providing
network connection and query it. That range isnt intended for general

My guess is that those DNS servers are not accessible - When the WiFi
connects it hands out a working DNS server, so that afterwards that
server is used even when eth0 is used. (Both eth0 and WiFi are reported
as using the same range and route.)
A little more information about the network, and the source of WiFi would
be helpful.

Wow! It works! I’ll read that thread and I’ll try to understand better the problem and the solution.

Thanks to everybody. Definitely this community is one of the best parts of Qubes.

1 Like