VPN on Gateway: no route to host

Support
1

Hello,

I’ve been using VPN on Whonix Gateway since v9. It’s been working on v10, v11 but after upgrading to recent version (v13) I can’t make openvpn to connect with my vpn server.

OpenVPN log says “no route to host”.

Has anything changed ?

2

Yes. Follow the documentation.

3

“Use VPN-Firewall outside of Whonix only!”

I’m used to configure fail closed mechanism on Gateway. It’s not possible anymore?

4

It’s possible. Just follow the documentation link I posted above.

(And stay away from VPN-Firewall which is indeed for outside of Whonix
only but which is no issue since Whonix as a fail closed mechanism
integrated - see documentation on how to use.)

5

ok, connection with VPN server works now, tun0 is active.

However I encouraged another problem. I followed

explaining how to set up fail closed mechanism on Gateway.

when doing “make deb-icup”

####################################################################

BEGIN ERROR in ./make-helper.bsh detected!

ERROR LOG:

See above.

BASH_COMMAND: debuild --no-lintian ${make_use_gain_root_command_maybe_switch}${make_use_gain_root_command_maybe_path} -sa $make_debuild_maybe_unsigned_opts ${1+“$@”}

EXIT_CODE: 127

END ERROR in ./make-helper.bsh detected!

Please report this bug!

####################################################################
’
++ ‘[’ ‘!’ 1 = 1 ‘]’
++ ‘[’ ‘!’ 1 = 1 ‘]’
++ ‘[’ ‘!’ 1 = 1 ‘]’
++ exit 1
Makefile:55: recipe for target ‘deb-icup’ failed
make: *** [deb-icup] Error 1

So it seems I can’t compile it.

6

I already said do NOT use VPN-Firewall on Whonix-Gateway. It is neither
required nor necessary. Just read the documentation and it will not
advice VPN-Firewall.

First read:

Then you end up on either:

or:

It does NOT suggest to use VPN-Firewall. And that documentation explains
how to set up the Whonix TUNNEL_FIREWALL feature.