testing: Reorganizing IKEv1 and IKEv2 examples

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.
This commit is contained in:
Andreas Steffen
2021-05-21 09:42:50 +02:00
parent db93938297
commit 7c5a2974b9
4054 changed files with 16375 additions and 15209 deletions
+9 -8
View File
@@ -1,10 +1,11 @@
The roadwarriors <b>carol</b> and <b>dave</b> set up a connection each to gateway <b>moon</b>.
Both <b>carol</b> and <b>dave</b> request a <b>virtual IP</b> via the IKEv1 Mode Config payload
by using the <b>leftsourceip=%config</b> parameter. The gateway <b>moon</b> assigns virtual
IP addresses from a simple pool defined by <b>rightsourceip=10.3.0.0/28</b> in a monotonously
increasing order.
Both <b>carol</b> and <b>dave</b> request a <b>virtual IP</b> via the IKEv1 Mode Config
payload by using the <b>vips = 0.0.0.0</b> parameter.
<b>moon</b> assigns virtual IP addresses from a simple pool defined in the pools section
of swanctl.conf in a monotonously increasing order.
<p>
<b>leftfirewall=yes</b> automatically inserts iptables-based firewall rules that let pass
the tunneled traffic. In order to test the tunnels, <b>carol</b> and <b>dave</b> then ping
the client <b>alice</b> behind the gateway <b>moon</b>. The source IP addresses of the two
pings will be the virtual IPs <b>carol1</b> and <b>dave1</b>, respectively.
Upon the successful establishment of the IPsec tunnel, the updown script automatically
inserts iptables-based firewall rules that let pass the tunneled traffic. In order to
test the tunnels, <b>carol</b> and <b>dave</b> then ping the client <b>alice</b> behind
the gateway <b>moon</b>. The source IP addresses of the two pings will be the virtual
IPs <b>10.3.0.1</b> and <b>10.3.0.2</b>, respectively.