Thursday 20 February 2014

Softether VPN client default route

Softether VPN Client

I've been using the built in Windows VPN client (L2TP) to connect to my VPN server, but had a problem with the MAC Address changing, thus was unable to assign a static one via DHCP.

To overcome this, I swapped to using the Softether Client, but discovered another issue.

I wasn't able to stop the VPN becoming my default route. It became THE gateway for all of my internet traffic... Something that I didn't want to happen. I'm using this to provide remote access to servers, not to hide my internet traffic, so I don't want it going half way across the world before getting out of the building.

There doesn't seem to be an obvious toggle to change this behaviour in the client software unlike the nice tick box that Microsoft provide, but I have discovered a work-around.

This is working for myself and a colleague, but YMMV. If there is a better way, please do let me know!

It involved a couple of steps:

  • In softEther VPN Client Manager edit the Properties of your VPN. On the Advanced Settings... button, tick the No Adjustments of Routing Table under Other Configurations.
  • Run ncpa.cpl (Network Connections from Control Panel)
  • Edit the Properties of your VPN Client Adapter. Change the IPv4 TCP/IP settings; under Advanced change the Interface metric to 100 (for example)
  • Edit the same value for the NIC you want to use for your internet and change it to a really low number. I used 1 for LAN and 2 for WiFi.
Test! You can check the routes and metric values from a command prompt using route print

This certainly worked for me and doesn't seem to have impacted my LAN sessions, even when the VPN is not connected.
It's not ideal, but if you find yourself in the same situation, it might just help!

No comments: