I never got Qubes-VPN-Support by @tasket (tasket) to work with wireguard.
And qubes-tunnel is no different.
Followed all instructions.
root@sys-vpn:/home/user# cp user_config.ovpn /rw/config/qtunnel/qtunnel.conf
copying the mullvad wireguard config to qtunnel.conf
added qubes-tunnel in Service Tab to launch at VM Startup, nothing happened.
Troubleshooted with journalctl -u qubes-tunnel
and got the following:
Starting Tunnel service for Qubes proxyVM…
su[689]: (to user) root on none
su[689]: pam_unix(su-l:session): session opened for user user by (uid=0)
qtunnel-setup[1229]: START-ing network forwarding!
systemd[1]: Started Tunnel service for Qubes proxyVM.
qtunnel-setup[1228]: EXEC /usr/sbin/openvpn --cd /rw/config/qtunnel/ --config /tmp/qtunnel.conf --verb 3 --mlock --ping 10 --ping-restart 42 --connect-retry 5 30 --connect-retry-max 7 --resolv-retry 15 --gro>
qtunnel-setup[1232]: Options error: Unrecognized option or missing or extra parameter(s) in /tmp/qtunnel.conf:1: [Interface] (2.4.9)
qtunnel-setup[1232]: Use --help for more information.
systemd[1]: qubes-tunnel.service: Main process exited, code=exited, status=1/FAILURE
qtunnel-setup[1234]: STOP-ing network forwarding!
systemd[1]: qubes-tunnel.service: Failed with result ‘exit-code’.
systemd[1]: qubes-tunnel.service: Scheduled restart job, restart counter is at 1.
systemd[1]: Stopped Tunnel service for Qubes proxyVM.
I think it has to do with config or that qubes-tunnel thinks it is an openvpn config. Either way, been waiting to get wireguard working for 2 years on Qubes. I want a seamless autostart with built in kill switch anti leaks.
Both qubes-tunnel and Qubes-VPN-Support lack proper documentation to get wireguard running. I noticed Qubes VM Kernel 5.7 doesn’t come with wireguard, so had to install wireguard, wonder why Qubes Developers remove it from the kernel.