Closed secretmango closed 1 year ago
Try turning on local network sharing.
@eightfiftytwo thanks that solved it! I am confused now, isnt that also the setting to connect to other devices in the virtual local network, e.g. other of your devices on the same wireguard router?
Not sure what you mean by virtual local network and wireguard router, but here's what I figured out when I had the same problem.
By default, mullvad captures all traffic and sends them through the VPN tunnel, even traffic intended for private IP ranges like 192.168.0.0/16. So you can't reach devices on your LAN on 192.168.1.0/24.
Turning on 'local network sharing' lets you access your LAN by allowing traffic to LAN to bypass the tunnel. Unfortunately, the name is a bit misleading. Because what it actually does is allow traffic to all private IP ranges like 192.168.0.0/16 to bypass the tunnel. Since virt-manager runs its own subnet at 192.168.122.0/24, you need this option to reach the VM. Not sure what the networking situation is for waydroid, but it seems similar, just with 192.168.250.0/24.
See also this comment.
I'm a networking noob so don't take this as gospel
good explanation for a noob! Ticking this option fixed it
It only kinda works for me, I don't get a notification that I'm offline but everything ages to load and then just fails
update: after upgrading to Fedora 40 now it suddenly doesnt work anymore. Running mullvad-exclude virt-manager
it works normally.
I have local network sharing enabled.
Is there any port I need to open to make it work?
I have reset my systemd-resolved settings to vanilla, and still when connected to Mullvad VPN my VMs and Waydroid have no internet. When I disconnect the App I suddenly have internet again.
I use a Wireguard tunnel and use Mullvads DNS adblocking etc. What do I have to do to have internet in the containers too? Waydroid uses Android libraries to run Android apps in containers (not an emulator). Do I have to change their DNS servers?