For documentation purposes the new folders ikev1-algs, ikev2-algs, ikev1-multi-ca and ikev2-multi-ca have been created. Most of the test cases have now been converted to the vici interface. The remaining legacy stroke scenarios yet to be converted have been put into the ikev2-stroke-bye folder. For documentation purposes some legacy stroke scenarios will be kept in the ikev1-stroke, ikev2-stroke and ipv6-stroke folders.
13 lines
1.0 KiB
Plaintext
13 lines
1.0 KiB
Plaintext
The roadwarriors <b>carol</b> and <b>dave</b> set up a connection each to gateway <b>moon</b>
|
|
and request a <b>virtual IP</b> via the IKEv2 configuration payload by using the <b>leftsourceip=%config</b>
|
|
parameter. The <b>dhcp</b> plugin on gateway <b>moon</b> then requests an IP address and DNS/WINS server
|
|
information from DHCP server <b>venus</b> using the DHCP protocol. The IP addresses are assigned statically
|
|
by <b>venus</b> based on the user-defined MAC address derived by the <b>dhcp</b> plugin from a hash over
|
|
the client identity. This deterministic MAC generation is activated with the strongswan.conf setting
|
|
<b>charon.plugins.dhcp.identity_lease = yes</b>.
|
|
<p/>
|
|
With the static assignment of 10.1.0.30 and 10.1.0.40, respectively, <b>carol</b> and <b>dave</b>
|
|
become full members of the subnet 10.1.0.0/16 hidden behind gateway <b>moon</b>. And this thanks to
|
|
the <b>farp</b> plugin through which <b>moon</b> acts as a proxy for ARP requests e.g. from <b>alice</b>
|
|
who wants to ping <b>carol</b> and <b>dave</b>.
|