You are not logged in.
Sorry if this is the wrong category.
For about a month or two I've been unable to use the internet in my QEMU VMs. They appear to be being assigned an ipv6 address, which i can see typing ip addr on the guest os, however I can't ping with it because it says "name or service not known".
I am able to get internet fine using Virtualbox, and I've tried this with multiple VMs with no luck.
ip link reads
[koplayz@kparchII]➜ (~): ip link
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: enp14s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc fq_codel state DOWN mode DEFAULT group default qlen 1000
link/ether 34:5a:60:3a:a7:01 brd ff:ff:ff:ff:ff:ff
altname enx345a603aa701
3: br0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN mode DEFAULT group default qlen 1000
link/ether ee:43:25:62:98:86 brd ff:ff:ff:ff:ff:ff
4: wlp15s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DORMANT group default qlen 1000
link/ether 0e:7f:f3:4c:88:11 brd ff:ff:ff:ff:ff:ff permaddr c8:a3:e8:b2:f2:b1
altname wlxc8a3e8b2f2b1
5: virbr0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000
link/ether 52:54:00:08:a2:43 brd ff:ff:ff:ff:ff:ff
6: tailscale0: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu 1280 qdisc fq_codel state UNKNOWN mode DEFAULT group default qlen 500
link/none
7: docker0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN mode DEFAULT group default
link/ether a2:c7:9f:75:96:5c brd ff:ff:ff:ff:ff:ff
9: vnet1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master virbr0 state UNKNOWN mode DEFAULT group default qlen 1000
link/ether fe:54:00:be:93:f7 brd ff:ff:ff:ff:ff:ffAny help would be appreciated. Thanks!
Offline
It's a little confusing to look at a system with (at least) three virtualization products (docker, VirtualBox, QEMU/libvirt), an unused bridge of unknown origin (br0) and a mesh network (tailscale) and find a cause for this phenomenon. Each of those products may have (or do have) unique quirks regarding your network setup and management - which we know nothing of.
Have you considered simplifying your Arch installation?
Offline