Hi everyone
I’ve been wrestling with setting up a template vm with Mullvad. I mean, like all day and I’m sort of stuck.
Initially I followed Micah Lee’s guide: Using Mullvad VPN in Qubes
This set up pretty much perfectly except for two things
- Unless I’m reading his instructions incorrectly when I start my vm it doesn’t connect to Mullvad automatically. I get the network manager icon and I can connect via that, but it doesn’t connect automatically.
- I cannot get any other app vm to go via this newly created mullvad vm. When I try to route another vm via this I get a warning about problematic networking with regard to the disposable vm. The Yellow triangle with an exclamation mark.
I could not see what I had wrong that stopped other vms going via this newly created template vm with mullvad. The vm works ok in that I can launch a browser from within the newly created one and it is connecting via Mullvad.
So if anybody has an idea what I’m now doing here I’d appreciate it.
So not to be outdone I then went to the Mullvad guide here: Mullvad on Qubes OS 4 - Guides | Mullvad VPN
I have followed this one and its all good so far except for getting a vif ip address under the section “Add DNS hijacking script”. Either I am too tired, or this is beyond me but can anybody tell me what this means:
“To find out your vif* ip address, run ip a | grep -i vif
in a terminal (make sure you have the AppVM assigned before you do this, otherwise it will not show up)”?
I am not getting anything to show up which I assume is because I haven’t assigned the AppVm.
Can anybody tell me what assigning the AppVm means? If I can get this I can power on through it I hope.
Networking is hard for me so I hope I’m not asking questions that are too basic.
If you have read this, I thank you. If you could offer me a pointer or two even better. i have the Micah Lee version still set up so if I can find out why I can’t get App VMs to go through it, great. If not I’ll go on with the Mullvad guide (if I can just learn how to assign this AppVm.