Changes between Version 29 and Version 30 of HLKTesting

Timestamp:

05/09/19 09:43:09 (5 years ago)

Author:

jamallx

Comment:

--

HLKTesting

@@ -176 +176 @@
 }}}
 
+== Peer to Peer OpenVPN setup for HLK ==
+
+The following was tested with Windows 10 x64 and worked well. 
+
+What you need:
+1) HLK Controller (Tested With: Windows Server 2012 R2 on VMWare and Installed HLK tools on that)
+2) Two Test Machines that have similar performance characteristics (preferably exactly same builds)
+
+Setup Steps:
+1) On both test Machines Install the OS you want to test on. This must match the HLK tools you installed on your controller.
+2) On both test machines Install OpenVPN. Only the service is needed.
+
+In the C:\Program Files\OpenVPN\config directory on each machine add configurations for a peer to peer static key configuration by following the steps here: [https://openvpn.net/community-resources/static-key-mini-howto/]. However instead of dev tun use dev tap and make the needed changes to ifconfig. Examples below:
+
+server.ovpn
+{{{
+dev tap
+ifconfig 10.1.1.1 255.255.255.0
+secret static.key
+}}}
+
+client.ovpn
+{{{
+dev tap
+remote <IP FOR SERVER>
+ifconfig 10.1.1.2 255.255.255.0
+secret static.key
+}}}
+
+On each machine set the OpenVPN Legacy Service to Automatic.
+
+Reboot and ping each host to make sure everything is working. You are now setup to run the WHQL tests. Some of them need babysitting and are listed below:
+
+1c_FaultHandling: At the end of the test the Service might not re-establish a link. WHQL seems to get it into a bad state, just restart the service and the test will pass. The test waits a few minutes for the link to come back up.
+
+2c_Mini6Stress: Sometimes this will hit a breakpoint in the NDIS test code. The breakpoint seemed harmless and complained about soem packents not getting confirmed. If you don't connect a kernel debugger this will cause a BugCheck and the test will fail. If this happens connect a kernel debugger and rerun the test. When the breakpoint is hit press (l) Always Ingore and the test will pass.
+
+2c_Priority: Follow the directions for using tapdiag in this document.
+
+AddressChange: This will definitley fail on slower machines. It worked fine on 1 year old i7 systems.
+
+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.
+
+Some HLK Errata:
+* The controller seems to arbitratily pick which machine is Support and which one is under Test. Even picking the options in the UI didn't change the behaviour. So for the tests you are baby sitting pay attentions to which the server and and which the client it. The server will run a server.htm in NDIS test so it will be obvious.
+
+* Reboots seems to happen randomly during test setup. This can be a nusiance if you are monitoring the services window or the network connections window. Helpful to make shortcuts to these so they can easily be opened.
+
+* In the HLK Studio. You will see a category called Product Types. This may not have anything listed. If this is the case you will do all this work and only get certified as an "Other Driver". Make sure it says LAN. I had to go back to the Selection Tab, right click on the TAP adapter and add the feature for Device.Network.LAN.PM (power management). This will add a few tests but all should pass.
+
+* End to End testing can take about 5 hours because of baby sitting. Pick a good book to read or have some other work handy to keep you from losing your mind :).
+
+Not sure if the below had any effect but was changed when doing this test:
+
+In OemVista.inf.in: *PhysicalMediaType = 0x0 ; NdisPhysicalMediumUnspecified
+
+This was done to be consistant whith what was in constants.h, but it also seemed to get some tests passing.
+
 == Testing OpenVPN connectivity ==