Virtual IP » History » Version 11
- Table of contents
- Virtual IP
IKEv1 and IKEv2 both know the concept of virtual IPs. This means that the initiator requests an additional IP address from the peer to use as inner IPsec tunnel address.
In IKEv1, virtual IPs are exchanged using the mode config extension. IKEv2 has full support for virtual IPs in the core standard using configuration payloads.
strongSwan currently implements one scenario with configuration payloads, where an IP address is assigned to the initiator (since 5.0.1 multiple addresses can be assigned from multiple pools). The opposite is possible by the protocol, but is an uncommon setup and therefore not supported.
The client needs an additional parameter called leftsourceip.
%config means to request an address from the responder and is an alias for the IKEv1 specific %modecfg. But you may specify an address explicitly by setting:
This will include 10.3.0.5 into the configuration payload request. However, the responder may return a different address, or may not return one at all.
Since 5.0.1 a client may request multiple IP addresses by listing a comma-separated combination of %config4, %config6 or fixed IP addresses in leftsourceip. Configuring %config (or one of its aliases) will request an address of the tunnel address family.
The main use case is for dualstack hosts to request a virtual IP of each address family:
leftsourceip=%config4,%config6This is also illustrated in the ikev2/ip-two-pools-v4v6 test scenario.
leftsubnet option should not be included when requesting a virtual IP, as the subnet may not match the received address. Without the leftsubnet option, the subnet is narrowed to the assigned virtual IP automatically.
Before 5.0.1 the client couldn't explicitly request other attributes, but it may still have processed the DNS attribute. With current releases DNS servers may explicitly be requested with the leftdns option. Received DNS servers are handled, for instance, by the resolve plugin which writes them to /etc/resolv.conf, or an other file specified with the --with-resolve-conf configure directive.
The responder configuration uses the rightsourceip option:
This will serve the IP 10.3.0.6 to the client, even if the initiator requested another address. Additionally, the responder may define:
to let the client choose an address. This is not recommended if you do not trust the client completely.
You may define an address pool in CIDR notation, e.g.
rightsourceip=10.3.0.0/24to serve addresses from that pool.
You may also use an external pool implemented as a plugin where you can specify a pool name to select addresses from. The definition
queries registered plugins for an IP from a pool named poolname. This can also be the name of another connection in ipsec.conf which defines a pool in CIDR notation with rightsourceip, as a pool with that connection's name is created implicitly. Since 5.0.1 multiple connections (i.e. conn sections) can share the same pool implicitly if they use the same definition in rightsourceip (previously each connection would use it's own copy and the same virtual IP may have been handed out to different clients).
Multiple pools can be listed in rightsourceip since 5.0.1, e.g.
As used in the ikev2/ip-two-pools-v4v6 test scenario.
With the dhcp plugin the responder can request virtual IP addresses for clients from a DHCP server using broadcasts, or a designated server.
DNS/WINS server information is additionally served to clients if the DHCP server provides such information.
The plugin is used in ipsec.conf configurations by setting
The farp plugin might also be of use when using the dhcp plugin. It allows the responder to fake ARP responses for virtual IP addresses handed out to clients. This lets a road-warrior act as a client on the local LAN of the responder.
Versions before 5.0.0¶
The description above covers the features of the charon daemon, which handled only IKEv2 connections in earlier releases. The pluto daemon that handled IKEv1 connections provided a similar feature set but not everything was supported (for instance, the dhcp and farp plugins).
The pluto daemon did not request virtual IP addresses from the responder if they were explicitly configured with leftsourceip. In that case, that is, if the virtual IP was not assigned by the responder with rightsourceip one may had to use the rightsubnetwithin directive (refer to this example).