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:
@@ -4,12 +4,11 @@ The key exchange is based on NTRU encryption with a cryptographical strength of
|
||||
algorithm with strengths 128 bits (BLISS I), 160 bits (BLISS III) and 192 bits (BLISS IV) for
|
||||
<b>carol</b>, <b>dave</b> and <b>moon</b>, respectively.
|
||||
<p>
|
||||
Both <b>carol</b> and <b>dave</b> request a <b>virtual IP</b> via the IKEv2 configuration 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
|
||||
Both <b>carol</b> and <b>dave</b> request a <b>virtual IP</b> via the IKEv2 configuration payload.
|
||||
The gateway <b>moon</b> assigns virtual IP addresses from the pool 10.3.0.0/28 in a monotonously
|
||||
increasing order.
|
||||
<p>
|
||||
<b>leftfirewall=yes</b> automatically inserts iptables-based firewall rules that let pass
|
||||
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>carol1</b> and <b>dave1</b>, respectively.
|
||||
|
||||
Reference in New Issue
Block a user