Source Routing#
NOTE: this is a WORK IN PROGRESS!
There are a number of situations to do source routing or policy routing.
- You already have a dedicated NAT router, i.e. CGNAT (“Carrier Grade NAT”);
- You have a (layer 2) connection to the target location from your VPN box where the VPN traffic needs to be sent over, i.e. when the VPN server is located outside the network where the traffic needs to go.
These require that you do not send the traffic from the VPN clients over the VPN server’s default gateway.
Luckily, it is relatively easy to fix. We document this for CentOS (and Fedora). We created a physical test setup similar to what you see below.
Internet
^
|
.--------.
| Router |
'--------'
^ 192.168.178.1
|
192.168.178.10 |
.--------. .--------.
| Client |--------->| Switch |<-------------------------.
'--------' '--------' |
VPN IP: 10.10.10.2 ^ |
| |
| |
192.168.178.2 | 192.168.178.3 |
.------------. .-----.
| VPN Server |-------------------->| NAT |
'------------' '-----'
10.10.10.1 192.168.1.100 192.168.1.1
Assumptions#
- Your VPN clients get IP addresses assigned from the
10.10.10.0/24
andfd00:4242:4242:4242::/64
pools, the VPN server has10.10.10.1
andfd00:4242:4242:4242::1
on thetun0
device; - A network connection between the VPN box and the NAT router exists through
another interface, e.g.
eth1
:- the VPN box has the IP addresses
192.168.1.100
andfd00:1010:1010:1010::100
on this network; - the remote NAT router has the IP addresses
192.168.1.1
andfd00:1010:1010:1010::1
on this network;
- the VPN box has the IP addresses
- You installed the VPN server using
deploy_centos.sh
ordeploy_fedora.sh
. - The network where you route your client traffic over has static routes
back to your VPN server:
- There is an IPv4 static route for
10.10.10.0/24
via192.168.1.100
; - There is an IPv6 static route for
fd00:4242:4242:4242::/64
viafd00:1010:1010:1010::100
;
- There is an IPv4 static route for
Source Routing#
We’ll need to add a new routing table in /etc/iproute2/rt_tables
, e.g.:
200 vpn
Rules#
First we test it manually, before making these rules permanent:
$ sudo ip -4 rule add to 10.10.10.0/24 lookup main
$ sudo ip -4 rule add from 10.10.10.0/24 lookup vpn
$ sudo ip -6 rule add to fd00:4242:4242:4242::/64 lookup main
$ sudo ip -6 rule add from fd00:4242:4242:4242::/64 lookup vpn
The to
rules are needed to make sure traffic between VPN clients uses the
main
table so traffic between VPN clients remains possible (if allowed by
the firewall).
Routes#
First we test it manually before making these routes permanent:
$ sudo ip -4 ro add default via 192.168.1.1 table vpn
$ sudo ip -6 ro add default via fd00:1010:1010:1010::1 table vpn
Making it permanent#
# echo 'to 10.10.10.0/24 lookup main' >/etc/sysconfig/network-scripts/rule-eth1
# echo 'from 10.10.10.0/24 lookup vpn' >/etc/sysconfig/network-scripts/rule-eth1
# echo 'to fd00:4242:4242:4242::/64 lookup main' >/etc/sysconfig/network-scripts/rule6-eth1
# echo 'from fd00:4242:4242:4242::/64 lookup vpn' >/etc/sysconfig/network-scripts/rule6-eth1
# echo 'default via 192.168.1.1 table vpn' > /etc/sysconfig/network-scripts/route-eth1
# echo 'default via fd00:1010:1010:1010::1 table vpn' > /etc/sysconfig/network-scripts/route6-eth1
When you use NetworkManager you need to install the package
NetworkManager-dispatcher-routing-rules.noarch
.
It is smart to reboot your system to see if all comes up as expected:
$ ip -4 rule show table vpn
32765: from 10.10.10.0/24 lookup vpn
$ ip -4 ro show table vpn
default via 192.168.1.1 dev eth1
$ ip -6 rule show table vpn
32765: from fd00:4242:4242:4242::/64 lookup vpn
$ ip -6 ro show table vpn
default via fd00:1010:1010:1010::1 dev eth1 metric 1024 pref medium
Firewall#
See the firewall documentation on how to update your firewall as needed.