Qubes-tunnel configuration with Mullvad bridges VPN

[kwebsfukr]

Has anyone been able to get the qubes-tunnel vpn working with mullvad openvpn configurations files that includes the check box for using bridges? I am getting these errors when running the (sys-vpn) qube.

● qubes-tunnel.service - Tunnel service for Qubes proxyVM
   Loaded: loaded (/lib/systemd/system/qubes-tunnel.service; enabled; vendor preset: enabled)
   Active: active (running) since Thu 2021-07-08 06:31:17 CDT; 2min 56s ago
  Process: 1263 ExecStartPre=/usr/lib/qubes/qtunnel-setup --check-firewall (code=exited, status=0/SUCCESS)
  Process: 1267 ExecStartPre=/usr/lib/qubes/qtunnel-setup --pre-start (code=exited, status=0/SUCCESS)
  Process: 1285 ExecStartPost=/usr/lib/qubes/qtunnel-setup --post-start (code=exited, status=0/SUCCESS)
 Main PID: 1284 (qtunnel-setup)
    Tasks: 2 (limit: 4648)
   Memory: 1.4M
   CGroup: /system.slice/qubes-tunnel.service
           ├─1284 /usr/bin/sh /usr/lib/qubes/qtunnel-setup --start-exec
           └─1288 /usr/sbin/openvpn --cd /rw/config/qtunnel/ --config /tmp/qtunnel.conf --verb 3 --mlock --ping 10 --ping-restart 42 --connect-retry 5 30 --connect-r

Jul 08 06:34:07 localhost qtunnel-setup[1284]: Thu Jul  8 06:34:07 2021 SIGUSR1[connection failed(soft),init_instance] received, process restarting
Jul 08 06:34:07 localhost qtunnel-setup[1284]: Thu Jul  8 06:34:07 2021 Restart pause, 5 second(s)
Jul 08 06:34:12 localhost qtunnel-setup[1284]: Thu Jul  8 06:34:12 2021 WARNING: you are using user/group/chroot/setcon without persist-tun -- this may cause restart
Jul 08 06:34:12 localhost qtunnel-setup[1284]: Thu Jul  8 06:34:12 2021 NOTE: the current --script-security setting may allow this configuration to call user-defined
Jul 08 06:34:12 localhost qtunnel-setup[1284]: Thu Jul  8 06:34:12 2021 TCP/UDP: Preserving recently used remote address: [AF_INET]127.0.0.1:1080
Jul 08 06:34:12 localhost qtunnel-setup[1284]: Thu Jul  8 06:34:12 2021 Socket Buffers: R=[131072->425984] S=[16384->425984]
Jul 08 06:34:12 localhost qtunnel-setup[1284]: Thu Jul  8 06:34:12 2021 Attempting to establish TCP connection with [AF_INET]127.0.0.1:1080 [nonblock]
Jul 08 06:34:12 localhost qtunnel-setup[1284]: Thu Jul  8 06:34:12 2021 TCP: connect to [AF_INET]127.0.0.1:1080 failed: Connection refused
Jul 08 06:34:12 localhost qtunnel-setup[1284]: Thu Jul  8 06:34:12 2021 SIGUSR1[connection failed(soft),init_instance] received, process restarting
Jul 08 06:34:12 localhost qtunnel-setup[1284]: Thu Jul  8 06:34:12 2021 Restart pause, 5 second(s)

[deeplow]

@kwebsfukr, I’ve added formatting to the post so it’s easier to read. You can also use the buttons in the post editor or learn some Markdown syntax to format it (which is a great skill to learn anyway).

[h110w]

Hi,
I don’t use the qubes-tunnel for my mullvad vpn instead I chose to use this method posted by Michah Lee. It works perfectly.

Using Mullvad VPN in Qubes

Hopefully this helps

Hayden

[deeplow]

There is also this guide which is similar:

How to setup OpenVPN + Fedora(AppVM) for OVPN

1. Create a new qube with these settings: Type: AppVM Template: Fedora Networking: sys-firewall Advanced: check “provides network” and “launch settings after creation” [1] 2. When the created-qube window settings showsup, go directly to tab “Services” 2.1 Select the service “network-manager” then click “+” to add the respective service 2.2 Check the “network-manager” field box then “Apply” → “OK” [2] 3. Download the vpn config file from ovpn website (this guide used the ‘finland’ ovpn…

[kwebsfukr]

Thank you! @deeplow

[Sven]

Thanks for the link/hint. I switched to the Micah Lee method from
qubes-tunnel because I actually understand what is going on. The bash
script that keeps the VPN up as well as using the firewall to ensure the
VPN proxy qube cannot connect to anything but the VPN servers. And yes
having the little lock icon in the task bar is a very nice touch too.

This method is in no way specific to Mullvad but can be used with any
OpenVPN setup.