Here’s notes for future readers and some questions:
- Update by Qubes Updater immediately post-install
for mullvad-dvm disposable
- Update browser in
mullvad-dvmtemplate. Update Mullvad extension too. - Account number and settings (<- ?) will not be recalled for each instance of
mullvad-dvmdispVM.
Each login creates a new device on your Mullvad account. They build up, so they will have to be deleted/logged out of later (easy in the app, apparently not so in the cli). Tip - learn the names of your other existing devices so you don’t accidentally log them out.
For sys-mullvad service as netVM
Currently, I cannot get this to work on my system. Tried several approaches, using Mullvad cli and the app.
sys-mullvadhas no memory of previous settings, no autostart of app.template-mullvad>$ /opt/'Mullvad VPN/mullvad-guilaunches app, but can’t log in so no settings are available (autostart). Didn’t bother trying withcli.- even when app or cli used to manually log in to Mullvad on
sys-mullvad, client AppVMs aren’t connecting to anything.
I thought of perhaps putting something in rc.local, but I see there are issues there that I do not understand and don’t want to screw with.
If there are instructions for this, can I suggest they are placed in the description for this package in Qubes Task Manager? Right now, I don’t know where to look.
Notes on user experience
After a couple of hours of experimentation, I’ve had to kill the mullvad-vpn dispVM a few times now. The browser seems to place a really high CPU and memory demand and freezes. Are the default settings adequate for this qube?
Video playback is a challenge (although may be a problem with NoScript and uBlockOrigin settings), but e.g. youtube has no sound. I think this is currently the same in TorBrowser in Qubes (known issue).
Qubes question: Surprised actually that the template has what seems to be full access to the web. I thought templates were special and restricted? Is that different here in this setup specifically or is that because its a named dvm template?