Files
strongswan-ext/testing/tests/ikev1/rw-multi-ciphers/description.txt
T
Andreas Steffen 7c5a2974b9 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.
2021-05-21 09:42:50 +02:00

16 lines
875 B
Plaintext
Executable File

The roadwarriors <b>carol</b> and <b>dave</b> set up a connection each
to gateway <b>moon</b>. The IKEv1 main mode authentication is based on
<b>X.509 certificates</b>.
On the gateway two connections with differing parameters are defined:
One for <b>carol</b> using the IKE proposal <b>aes128-sha256-modp3072</b>
allowing to reach host <b>alice</b> and one for <b>dave</b> using
the IKE proposal <b>3des-sha1-modp2048</b> allowing to reach host <b>venus</b>.
<p/>
Since the IP addresses of <b>carol</b> and <b>dave</b> are not known
to <b>moon</b> the matching connection definition can only be determined
by <b>moon</b> after the peer identities have been received.
<p/>
Upon the successful establishment of the IPsec tunnels, <b>carol</b> pings the
client <b>alice</b> and <b>dave</b> the client <b>venus</b> lying in two different
subnets behind the gateway <b>moon</b>.