Hi Jon,
Il 27/06/2018 00:11, Jon Kunkee ha scritto:
>
> Hi,
>
>> as a quick note - sorry, we won't make "June 27" as release date for
>> the new tap driver.
>
>> We tentatively plan for "one more week" now, which would be July 4th.
>
> No worries. Thanks for the update!
>
>> The Windows HLK tests for Server 2016 are somewhat
>> "demanding" from what I hear from Samuli (you need to have a larger
>> setup than "just the machine with the driver", it actually wants to
>> talk through the driver to "things" - which need to be provisioned,
>> etc.).
>
>> Jon, do you have experience with the HLK test suite and could help
>> explain some of the test failures ("what does the system expect to
>> find here?") - what's remaining does not seem to be "driver" related
>> but "things the tests expect to see in the network behind that driver"...
>> gert
>
> I have experience running the PCI portion of the HLK from Windows 8, so
> that gives me the basic idea. Those tests required two machines: the
> one with the device and the driver and the one with the HLK server.
>
> Network device testing is more complex because the test needs to control
> both the OS' end of the traffic and the external traffic. I found this:
>
> https://docs.microsoft.com/en-us/windows-hardware/test/hlk/testref/lan-testing-prerequisites
> (apologies if Exchange or Outlook mangles that link... ):
>
> It appears that you need three devices: the HLK server, the device with
> the 'hardware' and the driver for testing ('Test Machine' with a 'message
> device'), and the external traffic source/sink ('Support Machine'). All
> three probably need a backchannel link to the HLK server, while the Test
> Machine and Support Machine do best with a dedicated link through the
> device whose driver is being tested.Our test environment currently has the following nodes: - One combined HLK Studio/controller - Four identical HLK client nodes - OpenVPN test server The HLK nodes are all Windows Server 2016 as that is our primary target. The OpenVPN test server provides the HLK clients with an IPv6 address and IPv6 gateway - this is required for almost all "Run" tests. All of the nodes are in Amazon EC2. With the above setup 54 tests pass and 9 fail. The "Support machine" you mentioned is still missing. I will try to set it up today and check how many of the currently failing tests start passing. Note that right now I'm running the tests against tap-windows-9.22.1 to give us a baseline. That way we can check if our recent updates have broken (or possibly fixed) something. With 4 HLK clients the runtime of the whole test suite is almost reasonable. With one node it took 10+ hours. > > There should be a predefined set of individual tests that are required > by the signature service, probably NDISTest 6.5. > > I'd be happy to review failure logs to help figure out what's going wrong. > I can definitely grant you access to the HLK controller so that you can check what is happening. If you're working today around 16:00-18:00 UTC please poke me at #openvpn-devel and we'll get you started. -- Samuli Seppänen Community Manager OpenVPN Technologies, Inc irc freenode net: mattock
signature.asc
Description: OpenPGP digital signature
------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________ Openvpn-devel mailing list Openvpn-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openvpn-devel
