Virtual IP » History » Version 12

Tobias Brunner, 09.10.2012 10:56

1 6 Martin Willi
h1. Virtual IP
2 1 Martin Willi
3 11 Tobias Brunner
4 1 Martin Willi
5 10 Tobias Brunner
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.
6 1 Martin Willi
7 6 Martin Willi
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_.
8 6 Martin Willi
9 11 Tobias Brunner
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.
10 1 Martin Willi
11 7 Tobias Brunner
12 11 Tobias Brunner
h2. Initiator Configuration
13 1 Martin Willi
14 6 Martin Willi
The client needs an additional parameter called _leftsourceip_.
15 6 Martin Willi
16 7 Tobias Brunner
17 1 Martin Willi
18 11 Tobias Brunner
19 11 Tobias Brunner
20 1 Martin Willi
_%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:
21 1 Martin Willi
22 1 Martin Willi
23 1 Martin Willi
24 11 Tobias Brunner
25 1 Martin Willi
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.
26 1 Martin Willi
27 11 Tobias Brunner
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.
28 11 Tobias Brunner
The main use case is for dualstack hosts to request a virtual IP of each address family:
29 1 Martin Willi
30 11 Tobias Brunner
31 11 Tobias Brunner
32 11 Tobias Brunner
</pre> This is also illustrated in the {{tc(ikev2/ip-two-pools-v4v6)}} test scenario.
33 6 Martin Willi
34 11 Tobias Brunner
The @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.
35 1 Martin Willi
36 11 Tobias Brunner
h3. DNS servers
37 3 Martin Willi
38 11 Tobias Brunner
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 [[resolveplugin|resolve plugin]] which writes them to _/etc/resolv.conf_, or an other file specified with the _--with-resolve-conf_ configure directive.
39 11 Tobias Brunner
40 12 Tobias Brunner
h3. Implementation
41 12 Tobias Brunner
42 12 Tobias Brunner
On Linux, the virtual IP addresses will be installed on the outbound interface by default (may be changed, since [[5.0.1]], with the _charon.install_virtual_ip_on_ option) and source routes will be installed in the routing table configured with _charon.routing_table_ in [[strongswan.conf]] (or [[Autoconf|./configured]] with _--with-routing-table_). The source routes force the use of the virtual IP when sending packets to the subnets in _rightsubnet_.
43 12 Tobias Brunner
44 11 Tobias Brunner
45 11 Tobias Brunner
h2. Responder Configuration
46 11 Tobias Brunner
47 1 Martin Willi
The responder configuration uses the _rightsourceip_ option:
48 1 Martin Willi
49 6 Martin Willi
50 5 Martin Willi
51 11 Tobias Brunner
52 1 Martin Willi
This will serve the IP _10.3.0.6_ to the client, even if the initiator requested another address. Additionally, the responder may define:
53 1 Martin Willi
54 1 Martin Willi
55 1 Martin Willi
56 11 Tobias Brunner
57 1 Martin Willi
to let the client choose an address. This is not recommended if you do not trust the client completely.
58 5 Martin Willi
59 11 Tobias Brunner
You may define an address pool in CIDR notation, e.g.
60 1 Martin Willi
61 6 Martin Willi
62 11 Tobias Brunner
</pre> to serve addresses from that pool.
63 11 Tobias Brunner
64 11 Tobias Brunner
You may also use an external pool implemented as a plugin where you can specify a pool name to select addresses from. The definition
65 1 Martin Willi
66 1 Martin Willi
67 11 Tobias Brunner
68 11 Tobias Brunner
69 11 Tobias Brunner
queries registered plugins for an IP from a pool named _poolname_. This can also be the name of another connection in [[IpsecConf|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. [[ConnSection|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).
70 11 Tobias Brunner
71 11 Tobias Brunner
Multiple pools can be listed in _rightsourceip_ since [[5.0.1]], e.g.
72 11 Tobias Brunner
73 11 Tobias Brunner
74 6 Martin Willi
75 1 Martin Willi
76 11 Tobias Brunner
As used in the {{tc(ikev2/ip-two-pools-v4v6)}} test scenario.
77 1 Martin Willi
78 11 Tobias Brunner
h3. DNS servers
79 1 Martin Willi
80 11 Tobias Brunner
DNS servers and other attributes can be assigned by plugins (e.g. the [[AttrPlugin|attr plugin]]) or since [[5.0.1]] directly in [[ipsec.conf]] by use of the _rightdns_ option.
81 11 Tobias Brunner
82 11 Tobias Brunner
h3. Database backend
83 11 Tobias Brunner
84 11 Tobias Brunner
The [[IpsecPool|ipsec pool]] utility allows to easily manage IP address pools and other attributes, like DNS servers, stored in an SQL database using the [[attrsql|attr-sql plugin]].
85 11 Tobias Brunner
86 11 Tobias Brunner
h3. DHCP backend
87 11 Tobias Brunner
88 1 Martin Willi
With the [[DHCPPlugin|dhcp plugin]] the responder can request virtual IP addresses for clients from a DHCP server using broadcasts, or a designated server.
89 1 Martin Willi
90 1 Martin Willi
DNS/WINS server information is additionally served to clients if the DHCP server provides such information.
91 7 Tobias Brunner
92 11 Tobias Brunner
The plugin is used in [[ipsec.conf]] configurations by setting
93 7 Tobias Brunner
94 8 Tobias Brunner
95 1 Martin Willi
96 8 Tobias Brunner
97 11 Tobias Brunner
The [[FARPPlugin|farp plugin]] might also be of use when using the [[DHCPPlugin|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.
98 11 Tobias Brunner
99 11 Tobias Brunner
100 11 Tobias Brunner
h2. Versions before 5.0.0
101 11 Tobias Brunner
102 11 Tobias Brunner
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).
103 11 Tobias Brunner
104 11 Tobias Brunner
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":
105 11 Tobias Brunner
106 11 Tobias Brunner
The IKEv2 daemon charon supports address pools since version [[4.2.1]], the IKEv1 daemon pluto gained support for this in [[4.4.0]].