Hey guys,
We are looking of creating an SD-WAN setup which would use peers with Network Links to establish connection to networks behind those peers for the rest of the VPN users inside a server.
Currently we have 3 VPN servers on the Pritunl Host, one of these servers has attached the Network Links, but strangely they get attached to all 3 hosts on the WebUI.
Strangely enough when I took a deeper look into the staging host I noticed the routes are strangely configured. Instead of the routes to be attached to 1 of the tunnels it applies the routes to multiple tunnels (2 different servers). Here is a sample output, currently the configuration is to apply all the Network Links to the 172.16.0.1 (tun71) :
10.10.11.0/24 via 172.16.0.1 dev tun71
10.10.12.0/24 via 172.16.64.1 dev tun72
10.10.13.0/24 via 172.16.64.1 dev tun72
10.10.14.0/24 via 172.16.64.1 dev tun72
10.10.15.0/24 via 172.16.64.1 dev tun72
10.22.3.0/24 via 172.16.0.1 dev tun71 proto static
10.22.4.0/24 via 172.16.0.1 dev tun71 proto static
10.22.5.0/24 via 172.16.64.1 dev tun72
10.22.6.0/24 via 172.16.0.1 dev tun71 proto static
10.22.7.0/24 via 172.16.0.1 dev tun71 proto static
10.22.8.0/24 via 172.16.64.1 dev tun72
10.22.9.0/24 via 172.16.0.1 dev tun71 proto static
10.22.10.0/24 via 172.16.64.1 dev tun72
Any ideas why this could be happening?
Another question that comes to my mind, is there an easy way to setup proper split tunneling on the user level, so only a specific user would get the routes with Network Links to be available in it’s configuration?
Thanks in advance!