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:
1 parent
db93938297
commit
7c5a2974b9
4054 files changed
+16375
-15209
No files matched your search
@@ -1,9 +0,0 @@
|
||||
The roadwarriors <b>carol</b> an <b>dave</b> set up a connection to gateway
|
||||
<b>moon</b>. At the outset the gateway authenticates itself to the client by
|
||||
sending an IKEv2 <b>RSA signature</b> accompanied by a certificate.
|
||||
<b>carol</b> and <b>dave</b> then use the <b>EAP-MD5</b> protocol to authenticate
|
||||
against the gateway <b>moon</b>. The user credentials of <b>carol</b>
|
||||
and <b>dave</b> are kept both on the local clients and the RADIUS server <b>alice</b>.
|
||||
<b>carol</b> possesses the RADIUS class attribute <b>Research</b> and therefore obtains
|
||||
access to the <b>research</b> subnet behind gateway <b>moon</b> whereas <b>dave</b>
|
||||
belongs to the class <b>Accounting</b> and has access to the <b>access</b> subnet.
|
||||
Reference in new issue
Block a user