From 9b8053a63a532fef1d3b4899e02e91d81c6e4e80 Mon Sep 17 00:00:00 2001 From: Andreas Steffen Date: Wed, 14 Mar 2012 08:46:52 +0100 Subject: [PATCH] edited description of tnc/tnccs-11-radius scenario --- testing/tests/tnc/tnccs-11-radius/description.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/testing/tests/tnc/tnccs-11-radius/description.txt b/testing/tests/tnc/tnccs-11-radius/description.txt index 46ed5f5841..83e5b96f31 100644 --- a/testing/tests/tnc/tnccs-11-radius/description.txt +++ b/testing/tests/tnc/tnccs-11-radius/description.txt @@ -7,7 +7,7 @@ At the outset the gateway authenticates itself to the clients by sending an IKEv The strong EAP-TTLS tunnel protects the ensuing weak client authentication based on EAP-MD5. In a next step the EAP-TNC protocol is used within the EAP-TTLS tunnel to determine the health of carol and dave via the IF-TNCCS 1.1 client-server interface. -The IMC and IMV communicate are using the IF-M protocol defined by RFC 5792 PA-TNC. +The communication between IMCs and IMVs is based on the IF-M protocol defined by RFC 5792 PA-TNC.

carol passes the health test and dave fails. Based on these measurements the clients are connected by gateway moon to the "rw-allow" and "rw-isolate" subnets, respectively.