Qubes-tunnel.service: Failed with result 'exit-code'?

User Support
,
1

I was sooo hoping I could get a sys-vpn setup without running into a problem but…

I thought I followed the directions but since its not working I guess not. here is what journalctrl is telling me, not that I understand :stuck_out_tongue:

May 30 07:12:23 debian-12-minimal systemd[1]: qubes-tunnel.service - Tunnel service for Qubes proxyVM was skipped because of an unmet condition check (ConditionPathExists=/var/run/qubes-service/qubes-tunnel).
-- Boot 01f4989ddeef42878af8772b4a4cc88d --
Jun 04 08:38:25 debian-12-minimal systemd[1]: qubes-tunnel.service - Tunnel service for Qubes proxyVM was skipped because of an unmet condition check (ConditionPathExists=/var/run/qubes-service/qubes-tunnel).
-- Boot 99cd000c9be5440d8d2a31fc7007ecaa --
Jun 04 08:41:06 sys-vpn-us systemd[1]: Starting qubes-tunnel.service - Tunnel service for Qubes proxyVM...
Jun 04 08:41:06 sys-vpn-us su[643]: (to user) root on none
Jun 04 08:41:06 sys-vpn-us su[643]: pam_unix(su-l:session): session opened for user user(uid=1000) by (uid=0)
Jun 04 08:41:07 sys-vpn-us su[643]: pam_unix(su-l:session): session closed for user user
Jun 04 08:41:07 sys-vpn-us systemd[1]: qubes-tunnel.service: Control process exited, code=exited, status=1/FAILURE
Jun 04 08:41:07 sys-vpn-us qtunnel-setup[691]: STOP-ing network forwarding!
Jun 04 08:41:07 sys-vpn-us systemd[1]: qubes-tunnel.service: Failed with result 'exit-code'.
Jun 04 08:41:07 sys-vpn-us systemd[1]: Failed to start qubes-tunnel.service - Tunnel service for Qubes proxyVM.
Jun 04 08:41:17 sys-vpn-us systemd[1]: qubes-tunnel.service: Scheduled restart job, restart counter is at 1.
Jun 04 08:41:17 sys-vpn-us systemd[1]: Stopped qubes-tunnel.service - Tunnel service for Qubes proxyVM.
Jun 04 08:41:17 sys-vpn-us systemd[1]: Starting qubes-tunnel.service - Tunnel service for Qubes proxyVM...
Jun 04 08:41:17 sys-vpn-us su[815]: (to user) root on none
Jun 04 08:41:17 sys-vpn-us su[815]: pam_unix(su-l:session): session opened for user user(uid=1000) by (uid=0)
Jun 04 08:41:17 sys-vpn-us su[815]: pam_unix(su-l:session): session closed for user user
Jun 04 08:41:17 sys-vpn-us systemd[1]: qubes-tunnel.service: Control process exited, code=exited, status=1/FAILURE
Jun 04 08:41:17 sys-vpn-us qtunnel-setup[821]: STOP-ing network forwarding!
Jun 04 08:41:17 sys-vpn-us systemd[1]: qubes-tunnel.service: Failed with result 'exit-code'.
2

I’m quite sure it’s because qubes-tunnel still uses iptables, which is not supported on Qubes 4.2.

If you still want something similar, use this: