Sending all traffic through VPN - with some to net_gateway

Got a problem with Viscosity or need help? Ask here!

hub3rt

Posts: 1
Joined: Tue Mar 11, 2014 4:09 am

Post by hub3rt » Tue Mar 11, 2014 4:18 am
I am new to Viscosity, but I have been trying to get it so that by default, all my traffic goes through the VPN (vpn_gateway), while I have a few exception addresses that I dont need bogging down my available bandwidth on the vpn (ie some video streaming). I have found many times on this forum explaining sending traffic two ways using the Networking tab, which has been fine and dandy if I configure discrete routes for everything. I want ALL traffic to go VPN unless I have added a rule though.

For testing sake, I just have something like whatsmyip.org through my net_gateway to see if I am truly out of the VPN based on the rule. If I uncheck the box for sending all traffic through VPN and create two rules, each to a different website which shows my IP - one through net_gateway, one through vpn_gateway - I get two different IPs as expceted.

From reading through it sounded like I just need to click the 'Send all traffic through VPN' box, then make some rules which would override that. Whenever I do this, however, I get all traffic through the VPN, regardless of the rules I put out. Do I need to configure a default gateway on the Networking tab? Any help would be much appreciated. Thanks!

Eric

User avatar
Posts: 1146
Joined: Sun Jan 03, 2010 3:27 am

Post by Eric » Tue Mar 11, 2014 10:36 am
Hi hub3rt,

You are correct, all you need to do is tick the Send all traffic over VPN option, then create some routes in the box below where the route is the IP of the website/server you don't want going through the VPN, Mask is 255.255.255.255 and gateway is net_gateway/Local Network Gateway. A default gateway isn't needed.

One thing to try is to set a low Metric in the routes you are setting, for e.g. 1. This might help get them higher on the route lookup list but this shouldn't be necessary, leaving the Metric blank when setting up should get the desired results as Windows should be looking for routes based on the most precise subnet mask first.

If you're still having problems, could you please send us a copy of your route table once connected (Start -> Run, cmd, Enter, type route print, enter) and we can see if anything sticks out.

Regards,

Eric
Eric Thorpe
Viscosity Developer

Web: http://www.sparklabs.com
Support: http://www.sparklabs.com/support
Twitter: http://twitter.com/sparklabs
2 posts Page 1 of 1