Files
strongswan-ext/testing/tests/ikev2-stroke/rw-eap-sim-radius/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
837 B
Plaintext

The roadwarriors <b>carol</b> and <b>dave</b> set up a connection to gateway <b>moon</b>.
At the outset the gateway authenticates itself to the clients by sending
an IKEv2 <b>digital signature</b> accompanied by an X.509 certificate.
<p/>
Next the clients use the GSM <i>Subscriber Identity Module</i> (<b>EAP-SIM</b>)
method of the <i>Extensible Authentication Protocol</i> to authenticate themselves.
In this scenario triplets from the file <b>/etc/ipsec.d/triplets.dat</b> are used
instead of a physical SIM card.
<p/>
The gateway forwards all EAP messages to the RADIUS server <b>alice</b>
which also uses static triplets.
<p/>
The roadwarrior <b>dave</b> sends wrong EAP-SIM triplets. As a consequence
the RADIUS server <b>alice</b> returns an <b>Access-Reject</b> message
and the gateway <b>moon</b> sends back <b>EAP_FAILURE</b>.