Cisco Meraki Client VPN only establishes full-tunnel connections, which will direct all client traffic through the VPN to the configured MX. As such, any content filtering, firewall or traffic shaping rules will apply to the VPN client's outbound traffic.
For remote teleworkers or users whose traffic should not be restricted in the same manner, clients can be configured to use a split-tunnel connection to direct traffic through the VPN only if necessary:
This article includes instructions for configuring split tunnel client VPN on Windows and Mac OS X. For standard Client VPN configuration on Windows and Mac OS X, please refer to our Client VPN setup guide. The rest of this article assumes a VPN has already been setup in this manner.
Note: This configuration involves manually adding entries to a client's route table, and should only be followed by users with a thorough understanding of routing mechanisms.
First, modify the properties of the VPN connection to not be used as the default gateway for all traffic:
Next, add routes for the desired VPN subnets. This should be done with the VPN tunnel connected:
route add <destination subnet> mask <subnet mask> 0.0.0.0 IF <VPN adapter number>
The above route will be deleted upon a reboot. To make the route persistent, append a -p flag to the command.
Use the same command, replacing "add" with "delete" to remove the route.
First, disable full tunnel (all traffic over the VPN):
Add a new route to local routing table:
Route add -net <destination subnet>/<subnet mask in CIDR notation> -interface <VPN interface>
Ex. "route add –net 192.168.128.0/24 –interface ppp0"
To verify that the route was added take a look at the routing table, the new subnet should now have an entry. The route table can be accessed by typing "netstat -r":
The route table will have to be modified depending on what networks will be accessed over the Client VPN (e.g. more than one network behind the concentrator). The interface will also have to be modified if there is more than one VPN configured on the client.
Now that the route is added, a trace route can be performed to verify the direction of the traffic. All internet traffic should head out the normal interface and all VPN traffic should head to the PPP interface.
Note: These steps will have to be entered each time the VPN is brought up, but they can be defined in a script to make the changes quickly when needed. The specific process for this will be highly dependent on the operating system, tools available, and administrator preferences.