You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Dialup VPN server for remote clients .
Each remote client has preconfigured data path subnets for IPSEC traffic. The subnet is part of the Phase2 selector for traffic. We want to avoid pre-configuration of this subnet (shown below) on the server side since we’re trying to scale this against thousands of remotes and many vpn servers
ndividual VTI for each remote client subnet – this is preferred
Test Setup:
Question 1: Is there a way we can have only one "leftid" for the all the remote clients (strongswan)?
One conn block on the libreswan server configuration for all the remote clients.
Question 2: Also when we set the "rightsubnet=0.0.0.0/0" (on the libreswan Server) the IPSec fail due to:
The first IPSec 01 connection is successful but the second IPSec 02 phase 2 fails and throws following error:
psec02"[1] 10.11.0.2 #10: cannot install eroute -- it is in use for "ipsec01"[7] 10.11.0.1 #11
Mar 9 15:55:33.178415: | delete inbound eroute 0.0.0.0/0:0 --0-> 0.0.0.0/0:0 => [email protected] (raw_eroute)
Objective of the Libreswan server setup :
Dialup VPN server for remote clients .
Each remote client has preconfigured data path subnets for IPSEC traffic. The subnet is part of the Phase2 selector for traffic. We want to avoid pre-configuration of this subnet (shown below) on the server side since we’re trying to scale this against thousands of remotes and many vpn servers
ndividual VTI for each remote client subnet – this is preferred
Test Setup:
Question 1: Is there a way we can have only one "leftid" for the all the remote clients (strongswan)?
conn ipsec01
Question 2: Also when we set the "rightsubnet=0.0.0.0/0" (on the libreswan Server) the IPSec fail due to:
The first IPSec 01 connection is successful but the second IPSec 02 phase 2 fails and throws following error:
conn ipsec01
Due to the above two limitation we have to define a conn: block on the libreswan server for every remote side client which we are trying to avoid.
Libreswan VPN Server for remote clients:
config setup
conn %default
conn ipsec01
conn ipsec02
Strongswan Remote Client Config:
config setup
conn %default
conn ipsec01
conn ipsec02
The text was updated successfully, but these errors were encountered: