reorganized ikev2/rw-eap-tnc scenarios

2010-12-12 12:51:14 +01:00
parent 146e9123a2
commit 458e7779a8
120 changed files with 64 additions and 25 deletions
@@ -2,8 +2,10 @@ The roadwarriors <b>carol</b> and <b>dave</b> set up a connection each to gatewa
 using EAP-TTLS authentication only with the gateway presenting a server certificate and
 the clients doing EAP-MD5 password-based authentication.
 In a next step the EAP-TNC protocol is used within the EAP-TTLS tunnel to determine the
-health of <b>carol</b> and <b>dave</b> via the <b>TNCCS 2.0 PB-TNC (RFC 5793)</b> client-server interface.
+health of <b>carol</b> and <b>dave</b> via the <b>TNCCS 2.0 </b> client-server interface
+compliant with <b>RFC 5793 PB-TNC</b>.
+<p>
 <b>carol</b> passes the health test and <b>dave</b> fails. Based on these measurements the
 clients are connected by gateway <b>moon</b> to the "rw-allow" and "rw-isolate" subnets,
 respectively.
-
+</p>
@@ -6,7 +6,6 @@ charon {
  plugins {
    eap-tnc {
      protocol = tnccs-2.0
-      max_message_count = 4
    }
  }
 }
@@ -6,7 +6,6 @@ charon {
  plugins {
    eap-tnc {
      protocol = tnccs-2.0
-      max_message_count = 4
    }
  }
 }
@@ -11,8 +11,6 @@ charon {
    }
    eap-tnc {
      protocol = tnccs-2.0
-      max_message_count = 4
-      recommendation_policy = any
    }
  }
 }