Tomáš Vojtášek vojty

Routing tips for VPNs on OS X

When VPNs Just Work™, they're a fantastic way of allowing access to a private network from remote locations. When they don't work it can be an experience in frustration. I've had situations where I can connect to a VPN from my Mac, but various networking situations cause routing conflicts. Here are a couple of cases and how I've been able to get around them.

Specific cases

Case 1: conflicting additional routes.

In this example the VPN we are connecting to has a subnet that does not conflict with our local IP, but has additional routes that conflict in some way with our local network's routing. In my example the remote subnet is 10.0.x.0/24, my local subnet is 10.0.y.0/24, and the conflicting route is 10.0.0.0/8. Without the later route, I can't access all hosts on the VPN without manually adding the route after connecting to the VPN:

	import {MDXProvider} from '@mdx-js/react';
	import {MDXComponents} from 'components/MDX/MDXComponents';
	import {Toc} from 'components/Toc/Toc';
	import * as React from 'react';

	export interface MarkdownProps<Frontmatter> {
	meta: Frontmatter;
	children?: React.ReactNode;
	}

	<?php

	use Doctrine\ORM\Mapping as ORM;
	use Doctrine\Common\Collections\ArrayCollection;

	/**
	* @ORM\Entity()
	* @ORM\Table(name="user")
	*/
	class User

	#! /bin/sh
	# Init. script for phantomjs, based on Ubuntu 12.04 skeleton.
	# Author: Anthony Lapenna <[email protected]>

	PATH=/sbin:/usr/sbin:/bin:/usr/bin
	DESC="Phantomjs service"
	NAME=phantomjs
	DAEMON=/usr/bin/$NAME
	PIDFILE=/var/run/$NAME.pid
	SCRIPTNAME=/etc/init.d/$NAME