qubes-tunnel VS Qubes-vpn-support

Github Source

I've tried using both with qubes-vpn-support and qubes-tunnel. Both of the setup instructions seem about the same. As I've read on a few forums, if I follow this guide but replace the Mullvad conf file with the one I was given above, it should work just as well.

Use qubes-tunnel; the setup is much easier.

Try qubes-tunnel-service instead, it should work a lot better out of the box. (Dunno if it has IVPN support, but, if IVPN support OpenVPN it should be fine).

Clone the following repo in /home/user: git clone https://github.com/tasket/Qubes-vpn-support

This is closely based on the Qubes-vpn-support project.

Yes you can do that. First clone a debian-11 template to something like "debian-11-vpn", then start it and install openvpn/wireguard and stop it. After that, create an AppVM (with provides network enabled) per provider based on that new template, you can choose to use Network Manager (by adding it in the services tab in the qube settings) or by using Tasket scripts. Once the 3 qubes are good to go, you can attach anything you want to them and it will proxy the traffic trough the VPN provider of your choice.

I rolled by own app-vm (debian 11 with wireguard). Set it to use sys-firewall. Used this tutorial: https://github.com/tasket/Qubes-vpn-support/wiki/Wireguard-VPN-connections-in-Qubes-OS

Qubes-vpn-support

# apt install git $ git clone https://github.com/tasket/Qubes-vpn-support.git # bash /home/user/Qubes-vpn-support/install

So if I understand correctly this guide should pretty much work after in doing debian-10:~$ sudo apt-get install wireguard wireguard-tools wireguard-dkms -t unstable