Issue #1165
StrongSwan Virtual Ip problem
Description
Hi,
I am trying to set up windows port with a linux server that has setup as supporting road-warrior clients (assigning virtual ips to clients). I have read below information from the wiki and understood this scenario is not supported for windows and installing virtual ip is failing on windows:
Beside some other limitations, the kernel-iph networking backend currently does not support the installation of virtual IP addresses. Such addresses are usually assigned to road-warrior clients, making the strongSwan Windows port not usable as client for this particular scenario.
My question is: Is there a way to work around this scenario? lets say I dont need a virtual ip on windows and I can use a psychical nic ip to set the tunnel. However, if I do this lets say configure the windows as a normal client the negotiation with the road warrior server fails and policy is not installed because it expects a virtual ip from the windows client.
is there a configuration option to let windows side to work without the virtual ip even though the ipsec server side is configured to support road warrior clients?
Thanks.
Related issues
History
#1 Updated by Tobias Brunner about 5 years ago
- Related to Feature #641: kernel-iph virtual IP support and IKE routing lookups ignoring IPsec routes added