NDT-DEV email list created

Revision: 553
Author:   

Date:     Mon Aug 29 08:04:07 2011
Log:      Added description of the Simple Firewall Test.
http://code.google.com/p/ndt/source/detail?r=553

Modified:
 /wiki/NDTTestMethodology.wiki

=======================================
--- /wiki/NDTTestMethodology.wiki       Fri Aug 26 08:41:02 2011
+++ /wiki/NDTTestMethodology.wiki       Mon Aug 29 08:04:07 2011
@@ -30,6 +30,26 @@

 === Simple Firewall Test ===

+The simple firewall test tries to find out any firewalls between the NDT  
client and the NDT server that will prevent connections to an ephemeral  
port numbers. The test is performed in both directions (i.e. the NDT client  
is trying to connect to the NDT server and the NDT server is trying to  
connect to the NDT client).
+
+A detailed description of all of the SFW protocol messages can be found in  
the [NDTProtocol#Simple_firewall_test NDT Protocol document].
+
+As a first step both NDT components (the server and the client) bind an  
ephemeral port and notify the second component about this port number. In  
the second step both NDT components are executing in parallel:
+ # The client is trying to connect to the server's ephemeral port and send  
a TEST_MSG message containing a pre-defined string "Simple firewall test"  
of length 20 using the newly created connection.
+ # The server is trying to connect to the client's ephemeral port and send  
a TEST_MSG message containing a pre-defined string "Simple firewall test"  
of length 20 using the newly created connection.
+
+Both client and server are waiting for a valid connection a limited amount  
of time. If the MaxRTT or MaxRTO is greater than 3 seconds, than the time  
limit in the SFW test is 3 seconds. Otherwise the time limit in the SWF  
test is 1 second.
+
+The test is finished after the connection will be accepted or the time  
limit will be exceeded. If the time limit is exceeded, the firewall  
probably exists somewhere on the end-to-end path. If there is a connection  
and the pre-defined string is properly transferred, then there is no  
firewall on the end-to-end path. The third possibility is that there is a  
successful connection, but the expected pre-defined string is not  
transferred. This case does not adjudicate about the firewall existence.
+
+The possible simple firewall test result codes:
+
+|| *Value* || *Description* ||
+|| "0" || Test was not started ||
+|| "1" || Test was successful (i.e. connection to the ephemeral port was  
possible) ||
+|| "2" || There was a connection to the ephemeral port, but it was not  
recognized properly ||
+|| "3" || There was no connection to the ephemeral port within the  
specified time ||
+
 === C2S Throughput Test ===
  * A block of pseudo random data is generated on the client and stored in  
memory.
  * The client repeatedly transmits this data to the server for 10 seconds.