vpn_gateway Routing on Multiple Connections
Posted: Sat Oct 13, 2018 6:46 am
Hello!
I'm trying to set up connections to allow my developers to route traffic through two separate VPN servers. One of these servers has all of their addresses in the 10.0.0.0/24 CIDR block, and the other in the 11.0.0.0/24 block. Whenever I connect through either of them, it works just fine, but when I connect through both, I am unable to send traffic through the second connection.
Here are the relevant configuration settings for the two connections:
Connection 1 General:
Protocol: TCP
Device: tun
Connection 1 Networking:
Routing: IPv4 | Route: 10.0.0.0 | Mask/Bits: 255.255.0.0 | Gateway: vpn_gateway | Metric: Default
DNS Mode: Split
Servers: 10.0.0.8
Domains: rtx
Connection 2 General:
Protocol: TCP
Device: tun
Connection 2 Networking:
Routing: IPv4 | Route: 11.0.0.0 | Mask/Bits: 255.255.0.0 | Gateway: vpn_gateway | Metric: Default
DNS Mode: Split
Servers: 11.0.0.8
Domains: jnk
Additionally, here's the output of ifconfig that's generated by Viscosity:
utun10: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 1500
options=6403<RXCSUM,TXCSUM,CHANNEL_IO,PARTIAL_CSUM,ZEROINVERT_CSUM>
inet 192.168.255.6 --> 192.168.255.5 netmask 0xffffffff
utun11: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 1500
options=6403<RXCSUM,TXCSUM,CHANNEL_IO,PARTIAL_CSUM,ZEROINVERT_CSUM>
inet 192.168.255.6 --> 192.168.255.5 netmask 0xffffffff
I imagine that the issue is related to the inet being the same for both of these connections, but I'm not certain, nor am I sure what to do to resolve this. I'll continue poking at it & try to find a solution, but if anyone has any suggestions, it would be extremely appreciated!
I'm trying to set up connections to allow my developers to route traffic through two separate VPN servers. One of these servers has all of their addresses in the 10.0.0.0/24 CIDR block, and the other in the 11.0.0.0/24 block. Whenever I connect through either of them, it works just fine, but when I connect through both, I am unable to send traffic through the second connection.
Here are the relevant configuration settings for the two connections:
Connection 1 General:
Protocol: TCP
Device: tun
Connection 1 Networking:
Routing: IPv4 | Route: 10.0.0.0 | Mask/Bits: 255.255.0.0 | Gateway: vpn_gateway | Metric: Default
DNS Mode: Split
Servers: 10.0.0.8
Domains: rtx
Connection 2 General:
Protocol: TCP
Device: tun
Connection 2 Networking:
Routing: IPv4 | Route: 11.0.0.0 | Mask/Bits: 255.255.0.0 | Gateway: vpn_gateway | Metric: Default
DNS Mode: Split
Servers: 11.0.0.8
Domains: jnk
Additionally, here's the output of ifconfig that's generated by Viscosity:
utun10: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 1500
options=6403<RXCSUM,TXCSUM,CHANNEL_IO,PARTIAL_CSUM,ZEROINVERT_CSUM>
inet 192.168.255.6 --> 192.168.255.5 netmask 0xffffffff
utun11: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 1500
options=6403<RXCSUM,TXCSUM,CHANNEL_IO,PARTIAL_CSUM,ZEROINVERT_CSUM>
inet 192.168.255.6 --> 192.168.255.5 netmask 0xffffffff
I imagine that the issue is related to the inet being the same for both of these connections, but I'm not certain, nor am I sure what to do to resolve this. I'll continue poking at it & try to find a solution, but if anyone has any suggestions, it would be extremely appreciated!