SparkLabs Forum.

Community Help.

Route all trafic not working

Our own routerbox with PFsense with OpenVPN. LAN on 192.168.1.X
OpenVPN LAN 10.0.0.x
External IP:

Using Viscosity to connect in hotel rooms -> office server with PFsense. Main reasons security and my banking is locked to the office IP.

Now in a hotel that wants me to connect through their login page / proxy. Using viscosity and checking my IP, I still get the hotel IP.

Route all trafic.... is set to yes both IP4 and IPv6
Gateway has been set to the PFsense router.

It seems the tunnel is not working well when connecting though a hotel proxy? Thought the key of VPN was a secure connection and closed for others....

Did a trace route:

Traceroute has started…

traceroute to (, 64 hops max, 72 byte packets
1 * ( 3675.162 ms 2.705 ms
2 ( 5.672 ms 5.617 ms 5.428 ms
3 ( 23.732 ms 4.825 ms 9.526 ms
4 ( 7.018 ms 9.881 ms 7.162 ms
5 ( 5.734 ms 5.849 ms 11.020 ms
6 ( 12.642 ms 24.747 ms 10.864 ms
7 ( 21.792 ms 32.253 ms 58.423 ms
8 ( 24.256 ms 10.959 ms 11.866 ms
9 ( 229.941 ms 354.745 ms 223.366 ms
10 ( 226.282 ms 217.504 ms 253.532 ms
11 ( 219.015 ms 261.125 ms 216.737 ms
12 ( 270.575 ms 268.582 ms 268.987 ms
13 * * *
14 * * *
15 ( 1831.369 ms 1049.456 ms 1588.247 ms
16 * * *
17 * * *

Any suggestions how to get this all secured and locked?

Thanks Bastiaan
Hi Bastiaan,

Typically hotels will require you to log into a "captive portal" to enable internet access, at which point you should be able to connect to your VPN connection normally. It shouldn't be necessary in almost all instances to enter any proxy details into Viscosity.

I'd recommend leaving the Default Gateway blank in the settings: depending on your VPN server's setup it's unlikely this is the normal LAN IP address of your router. The OpenVPN server should be pushing out the correct gateway to use. Likewise, also make sure your pfSense server is set up to handle all network traffic. While the All Traffic option will result in your traffic being routed through the VPN connection, the VPN server must be configured to handle this.

One thing to check is that the hotel's IP address range doesn't clash with the address range on your remote VPN network (e.g. if both networks are trying to use 192.168.1.x or 10.0.0.x they'll clash).

Finally, I'd recommend checking the connection log and look for any warning or error messages: ... envpn-log/

2 posts Page 1 of 1

Copyright © 2016 SparkLabs Pty Ltd. All Rights Reserved. Privacy Policy