- Helm, SwitchHosts, or another hosts manager
Why use a VPN? The VPN will keep your network traffic secure between you and the host and will make snooping very challenging. The downside of a VPN is that all traffic from your computer is routed to the VPN host and you loose access to servers/websites that are on the local network.
These steps will help to make a VPN doable
Running intranet sites while on a VPN can be painful, but with a few steps can be conquered.
First install ProtonVPN and Helm.
ProtonVPN is the VPN of our choice.
Helm is used to easily manage hosts. We can have several profiles in there.
When you are running a VPN all network traffic is routed out to the VPN host. This means that you will not be able to access intranet sites anymore, or any sites that are specific to the network you are using.
Thankfully your mac has an option to router network traffic to specific hosts and bypass the VPN if needed!
A network route can be easily added. Here’s an example that will reroute all 10.x.x.x traffic through 220.127.116.11:
sudo route -n add -net 10.0.0.0 18.104.22.168
The problem is that when your mac restarts it will reset the routes!
We need to make a script that will add the routes each time your mac restarts.
In your favorite script location make a new script.
cd fav_script_location nano route_script
Add in the routes to add. You can find all the route syntax options by running
the basic syntax is
add route ip_address gateway_address
I include the -n so network names are not looked up when adding the route, and also -net which will allow a base address to include matches. For example -net 10.0.0.0 will include 10.1.0.0. The last three zeros are basically wild cards in the ip addresses.
To find the local gateway run
netstat -rn with the VPN off. The default destination will have a gateway IP address for you LAN.
When completed your script may look like this:
#!/bin/sh route -n add -net 10.0.0.0 10.1.123.1 route -n add -net 10.1.233.1 10.1.123.1
Change permissions for script.
chmod +x route_script
The plist needs to be in
/Library/LaunchDaemons to be picked up.
Add in the content.
<?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd"> <plist version="1.0"> <dict> <key>Label</key> <string>com.route_script.plist</string> <key>Program</key> <string>fav_script_location/route_script</string> <key>StandardErrorPath</key> <string>fav_script_location/route_script.err</string> <key>StandardOutPath</key> <string>fav_script_location/route_script.out</string> <key>RunAtLoad</key> <true/> <key>StartInterval</key> <integer>3600</integer> </dict> </plist>
Set the script to launch on startup.
sudo chown root /Library/LaunchDaemons/com.route_script.plist sudo launchctl load /Library/LaunchDaemons/com.route_script.plist
To test if the route are working you can manually start the plist, or restart your mac and run
netstat -rn. Your new rout should be listed in there!
To manually launch plist:
sudo launchclt start com.route_script.plist
If it does not start, open mac app “console” and check for any messages in the system.log section. You will find details of the errors in the paths specified for logging in the plist paths you created for logging.
Finally, the last step is to configure Helm with your hosts. Click the icon in the menu bar and follow instructions.
Turn on the VPN and try to access the local sites!