Changes between Version 36 and Version 37 of HLKTesting

Timestamp:

06/14/19 06:33:36 (5 years ago)

Author:

Samuli Seppänen

Comment:

--

HLKTesting

@@ -227 +227 @@
 
 
-LinkCheck, You don't need tapdiag for this. You can just start and stop the service when running this to make the link start and stop per the instructions.
 
 In general the rest of the tests passed without a problem. However, it was more successful doing groups at a time and making sure they passed.
@@ -273 +272 @@
 Some of the non-NDIS tests that require “a working network connection” can just be given a valid IPV6 address on the VPN network and they will be happy with that. Whenever you see the “WDTFREMOTESYSTEM” parameter when scheduling a test, set it to an IPv6 address the system can ping over the VPN link. This could be the ipv6 address of the “support” system, or it could be some other arbitrary system on the VPN. This might not be necessary if the device under test has a working IPv6 gateway address that points to, say, support machine's tap adapter interface. But wearing belt and suspenders is not a bad idea when running HLK tests.
 
+== NDISTest 6.5 - 2 machine - Linkcheck ==
+
+This test tests plugging and unplugging the (virtual) ethernet cable.
+
+For this test you have two options:
+
+* Start and stop the service when running this to make the link start and stop
+* Use Tapdiag to change link state on the test system
+
+Follow the interactive messagebox prompts. This test may need some delay after “reattaching” the cable.
+
 == NDISTest 6.0 - 2 Machine - 2c_Priority ==
 
-Use Tapdiag to enable 802.1Q on both machines before running the NDIS QoS test (2c_Priority), and use it to change link state on the test system for the LinkCheck (plug/unplug ethernet) test. Follow the interactive messagebox prompts, may need some delay after “reattaching” the cable.
+
+Use Tapdiag to enable 802.1Q on both machines before running the NDIS QoS test (2c_Priority). 
 
 The process for using tapdiag is: