Changes between Version 50 and Version 51 of HLKTesting


Ignore:
Timestamp:
06/20/19 12:35:45 (5 years ago)
Author:
Samuli Seppänen
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • HLKTesting

    v50 v51  
    6666The "Run tests" in HLK fail consistently unless the tap-windows6 adapter has an IPv6 gateway address. This can be resolved by a simple bridged peer to peer OpenVPN setup, where interface settings are configured statically outside of OpenVPN.
    6767
    68 First install the latest OpenVPN 2.x on the HLK client and support machine. Then install the same, test-signed (to-be-HLK-tested) tap-windows6 driver on the HLK clients. Then configure static IP, netmask, gateway, etc. for the TAP interface. Then generate a shared secret with "openvpn --genkey".
    69 
    70 The OpenVPN configuration files for HLK client and support machines can be identical except for the "remote" settings:
     68The first steps are:
     69
     70* Install the latest OpenVPN 2.x on the HLK client and support machine
     71* Install the same, test-signed (to-be-HLK-tested) tap-windows6 driver on the HLK clients
     72* Configure static IP, netmask, gateway, etc. for the TAP interface
     73* Disable Windows Firewall for the TAP adapter / Private networks. This is not strictly necessary, but saves time.
     74
     75Then generate a shared secret with "openvpn --genkey" so that you can use it in the OpenVPN config. The OpenVPN configuration file for HLK client and support machines can be identical except for the "remote" settings:
    7176
    7277{{{
    … …  
    8186The above setup is symmetric in the sense that neither node is a client or a server, and either one can initiate the connection. This is similar to what is described in the [https://openvpn.net/community-resources/static-key-mini-howto/ static key mini-howto].
    8287
    83 Once OpenVPN is configured properly make sure that OpenVPN is running and automatically starts on boot:
     88To verify OpenVPN connectivity launch it from an administrator Powershell session first on both machines:
     89
     90{{{
     91PS> cd C:\Program Files\OpenVPN\config
     92PS> ..\bin\openvpn.exe --config hlk.ovpn
     93}}}
     94
     95If you see that connection was established try to ping the VPN IPs (IPv4 and IPv6) of the other party from both ends. If that succeeds, you can stop OpenVPN and let OpenVPNService manage it from there on:
    8496
    8597{{{
    … …  
    89101Some have had more luck with the legacy service (OpenVPNServiceLegacy).
    90102
    91 Reboot and ping each host to make sure everything is working.
    92 
    93 
    94 
    95 Not sure if the below had any effect but was changed when doing this test:
    96 
    97 In OemVista.inf.in: *PhysicalMediaType = 0x0 ; NdisPhysicalMediumUnspecified
    98 
    99 This was done to be consistent with what was in constants.h, but it also seemed to get some tests passing.
    100 
    101 Changing the TAP interface type to be a virtual adapter did not work in this test pass. It seemed to mess up the NDIS tests which looked for a device that advertised as physical to assign a SupportDevice. Maybe this is something we can eventually work with Microsoft to fix.
     103
     104
    102105
    103106== Testing OpenVPN connectivity ==
    … …  
    352355The controller seems to arbitrarily pick which machine is Support and which one is under Test. If it has trouble picking name one of the TAP adapters SupportDevice0. Picking the options in the UI didn't change the behavior. So for the tests you are baby sitting pay attention to which the server and and which one the client is. The server will run a server.htm in NDIS test so it will be obvious.
    353356
    354 == Reboots ==
    355 
    356 Reboots seems to happen randomly during test setup. This can be a nuisance if you are monitoring the services window or the network connections window. Helpful to make shortcuts to these so they can easily be opened.
     357== Driver parameters ==
     358
     359Not sure if the below had any effect but was changed when doing this test:
     360
     361In OemVista.inf.in: *PhysicalMediaType = 0x0 ; NdisPhysicalMediumUnspecified
     362
     363This was done to be consistent with what was in constants.h, but it also seemed to get some tests passing.
    357364
    358365= HLK logging =
    … …  
    381388
    382389= Addendum =
     390
     391== Tap-windows6 as virtual network device ==
     392
     393Changing the TAP interface type to be a virtual adapter in the INF file does not seem to work. It seems to mess up the NDIS tests which looked for a device that advertised as physical to assign a SupportDevice. Maybe this is something we can eventually work with Microsoft to fix.
     394
     395== Note on reboots ==
     396
     397Reboots seems to happen randomly during test setup. This can be a nuisance if you are monitoring the services window or the network connections
     398window. Helpful to make shortcuts to these so they can easily be opened.
    383399
    384400== Firewall rules for HLK server and clients ==