Internet2 Detective Technical Information
This page explains the various tests that the Internet2 Detective software performs,
including Abilene connectivity, Bandwidth determination, Multicast Receiving capabilities. Additional information about using the Internet2 Detective with personal firewalls is also available.
|
|
|
1. Internet2 Detective, just started, on an Abilene connection.
|
2. Detective on a non-Abilene connection
|
3. Successful tests.
|
Abilene Connectivity
The Abilene Connectivity Test begins with the Internet2 Detective uses IP port
7777
to send a packet to a simple UDP echo server that is hosted on the Abilene backbone.
Immediately afterward, the Detective starts listening for a return packet. When the server receives a packet, it checks to make sure the packet came from the Detective, and if it did, it sends a special packet back.
If the Internet2 Detective receives this special packet in a timely manner, the Abilene Connectivity Test is considered successful. If the packet takes too long, is corrupted, or never arrives, the test fails.
Bandwidth Determination
The Bandwidth Measurement Test begins with the Internet2 Detective creating an instance of the NLANR Iperf in client mode. This client uses IP port
8888
to connect to an NLANR Iperf server hosted on the Abilene backbone, and performs a UDP bandwidth test for the amount of bandwidth specified. When the test finishes, the Detective parses the test's output, and uses the results to decide if the requested bandwidth was exceeded or not.
Multicast Reception Detection
The Multicast Reception Test begins with the Internet2 Detective connecting to the NLANR multicast beacon using
port 56464, and checking to see if any packets are received. If they are, then the test is considered successful. If, after a short period of time, no packets are received, the test fails.
Computer-to-Computer Bandwidth Test
A computer-to-computer network performance test begins with the Allow Connection Detective sending a packet to the Make Connection Detective, checking to see if the Make Connection dialog is open. If it is, the Make Connection Detective sends back an acknowledgement to the Allow Connection Detective. If the Allow side receives that packet, then the Allow side knows it can communicate successfully with the Make side. At this point, it is user-controlled.
The Make side user selects a number of parameters, starts an Iperf server, and then sends a packet which includes the parameters to the Allow side. When the Allow side receives said packet, it executes an Iperf client using the parameters contained in the packet body. This client talks to the Iperf server started by the Make side. Once the test is complete, the results are sent from the Allow side to the Make side, and are presented to the user. The computer-to-computer test uses IP port
6666.
|
