Virtual IP » History » Version 17

Noel Kuntze, 22.02.2016 14:39
pool range

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 15 Noel Kuntze
The @leftsubnet@ option defaults to the value @%dynamic@. If @leftsourceip@ respectively @rightsourceip@ is used, this value gets dynamically replaced by the received or assigned virtual IP.
28 15 Noel Kuntze
29 14 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.
30 14 Tobias Brunner
31 14 Tobias Brunner
To use a static virtual IP (i.e. without exchanging configuration payloads) it may simply be added to any local interface (even _lo_) and referenced in _leftsubnet_.
32 14 Tobias Brunner
33 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.
34 11 Tobias Brunner
The main use case is for dualstack hosts to request a virtual IP of each address family:
35 11 Tobias Brunner
36 11 Tobias Brunner
37 6 Martin Willi
38 11 Tobias Brunner
</pre> This is also illustrated in the {{tc(ikev2/ip-two-pools-v4v6)}} test scenario.
39 1 Martin Willi
40 11 Tobias Brunner
h3. DNS servers
41 3 Martin Willi
42 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.
43 11 Tobias Brunner
44 12 Tobias Brunner
h3. Implementation
45 12 Tobias Brunner
46 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_.
47 12 Tobias Brunner
48 11 Tobias Brunner
49 11 Tobias Brunner
h2. Responder Configuration
50 11 Tobias Brunner
51 1 Martin Willi
The responder configuration uses the _rightsourceip_ option:
52 1 Martin Willi
53 6 Martin Willi
54 5 Martin Willi
55 11 Tobias Brunner
56 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:
57 1 Martin Willi
58 1 Martin Willi
59 1 Martin Willi
60 11 Tobias Brunner
61 1 Martin Willi
to let the client choose an address. This is not recommended if you do not trust the client completely.
62 5 Martin Willi
63 11 Tobias Brunner
You may define an address pool in CIDR notation, e.g.
64 1 Martin Willi
65 6 Martin Willi
66 11 Tobias Brunner
</pre> to serve addresses from that pool.
67 11 Tobias Brunner
68 17 Noel Kuntze
Alternatively, you can define the pool as an address range:
69 17 Noel Kuntze
70 17 Noel Kuntze
71 17 Noel Kuntze
72 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
73 1 Martin Willi
74 1 Martin Willi
75 11 Tobias Brunner
76 11 Tobias Brunner
77 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).
78 11 Tobias Brunner
79 11 Tobias Brunner
Multiple pools can be listed in _rightsourceip_ since [[5.0.1]], e.g.
80 11 Tobias Brunner
81 11 Tobias Brunner
82 6 Martin Willi
83 1 Martin Willi
84 11 Tobias Brunner
As used in the {{tc(ikev2/ip-two-pools-v4v6)}} test scenario.
85 1 Martin Willi
86 11 Tobias Brunner
h3. DNS servers
87 1 Martin Willi
88 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.
89 11 Tobias Brunner
90 11 Tobias Brunner
h3. Database backend
91 11 Tobias Brunner
92 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]].
93 11 Tobias Brunner
94 11 Tobias Brunner
h3. DHCP backend
95 11 Tobias Brunner
96 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.
97 1 Martin Willi
98 1 Martin Willi
DNS/WINS server information is additionally served to clients if the DHCP server provides such information.
99 7 Tobias Brunner
100 11 Tobias Brunner
The plugin is used in [[ipsec.conf]] configurations by setting
101 7 Tobias Brunner
102 8 Tobias Brunner
103 1 Martin Willi
104 8 Tobias Brunner
105 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.
106 11 Tobias Brunner
107 13 Tobias Brunner
h3. RADIUS backend
108 13 Tobias Brunner
109 13 Tobias Brunner
Since [[5.0.3]] the [[EAPRAdius|RADIUS plugin]] can provide virtual IP addresses assigned to RADIUS clients via the Framed-IP-Address attribute.
110 13 Tobias Brunner
111 13 Tobias Brunner
The plugin is used in [[ipsec.conf]] configurations by setting
112 13 Tobias Brunner
113 13 Tobias Brunner
114 13 Tobias Brunner
115 11 Tobias Brunner
116 16 Tobias Brunner
h3. Multiple pools, different backends
117 16 Tobias Brunner
118 16 Tobias Brunner
If multiple pools are defined from different backends, for instance
119 16 Tobias Brunner
120 16 Tobias Brunner
121 16 Tobias Brunner
122 16 Tobias Brunner
123 16 Tobias Brunner
124 16 Tobias Brunner
the order in which they are queried for virtual IPs depends on the [[PluginLoad|plugin load order]] (in-memory pools are provided by the _stroke_ plugin). The order in _rightsourceip_ is irrelevant, unless, multiple in-memory pools are defined.
125 16 Tobias Brunner
126 11 Tobias Brunner
h2. Versions before 5.0.0
127 11 Tobias Brunner
128 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).
129 11 Tobias Brunner
130 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":
131 11 Tobias Brunner
132 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]].