Hi everyone,

I'm looking for some help as to how to diagnose some app-VM networking 
issues. I have 2 vms, both based on the same template with identical 
config, but one can reach the internet and the other cannot.

Before upgrading:
2 standalone VMs based on Fedora-30. One with a bunch of dev tools 
installed, one relatively untouched. I had multiple VMs based on these two 
templates. I also updated my sys-net and sys-firewall to Fedora-33 at the 
same time.

I upgraded to Fedora-33, and realised I could rationalise my VMs, so now 
every appVM is based off the same Fedora-33 template.

The issue:
Some of my migrated VMs are completely fine, others have no network. 
I _think_ it is the VMs that used to be based on my old "untouched" vm that 
have the issue. 

No networking at all.

Networking is completely fine, everything works as expected.

Both VMs are based on the same Fedora-33 template, with the same (default) 
sys-firewall Networking, both with the firewall configured to allow all 
outgoing internet connections

*vm1$ ping google.com*
ping: google.com: Name or service not known

*vm1$ dig google.com*
; <<>> DiG 9.11.35-RedHat-9.11.35-1.fc33 <<>> google.com
;; global options: +cmd
;; connection timed out; no servers could be reached

*vm1$ resolvectl dns*
Link 2 (eth0):

*vm2$ resolvectl dns*
Link 2 (eth0):
Link 3 (br-11bfb2cd10e9):
Link 4 (docker0):
Link 5 (br-cf58034d074b):
Link 6 (br-f9686c41a7f5):

So there's definitely something wrong, but I don't know enough about 
Linux/Qubes networking to work out what.

Any pointers gratefully received.

You received this message because you are subscribed to the Google Groups 
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to qubes-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 

Reply via email to