From: Simon Rozman <simon@...2293...>
Subject: Re: [Openvpn-devel] Summary of the community meeting (20th June 2019)
Date: Fri, 21 Jun 2019 15:59:43 +0000 [thread overview]
Message-ID: <FF8443AE-D430-496D-881A-C75171649BA6@...2293...> (raw)
In-Reply-To: <ef6133bb-cb4a-d70a-c0b4-1b9466fc19fd@...515...>
[-- Attachment #1: Type: text/plain, Size: 1821 bytes --]
(21:04:58) mattock: assuming Microsoft's systems are happy with the test submission package, that is
(21:05:12) mattock: they _should_ be, but we have not tested submitting anything yes
1. Do the SDV and DVL to get tap901.DVL.xml.
2. Compile the driver and EV sign it. Save PDBs too.
3. Deploy the driver on test computers (including tap901.DVL.xml, remember?).
4. Do the WHLK.
5. When creating submission package, add the driver binaries and PDBs (on HLK Studio submission page).
6. Submit the driver to Microsoft WHQL.
7. Miscrosoft should return you a WHQL signed driver in about 10 minutes.
(21:07:09) mattock: worst case scenario is that I have to reinstall the HLK client as Windows Server 2019 core _if_ Microsoft is not happy with the "Operate in Server Core" having been run on a virtual machine, or on some old i5 laptop which does not have the required 4 physical processor cores
Microsoft is fine with that test being run on a virtual Windows Server 2019 Core in Wintun case. And this test is pretty straight forward - just checks that driver loads and adapter responds, it doesn't need to be connected and have traffic. Use devcon to make a single TAP adapter on the Server Core. No need to have a running OpenVPN connection for this test to pass.
(21:14:42) mattock: I also finally ate our own dogfood and installer OpenVPN on the virtual host running the HLK controller so that I can access the HLK controller and clients remotely, which speeds the testing up quite a bit
Not a good idea, as WHLK tests can and will interfere with all TAP-Windows6 adapters on test computers. Not just the one that is being tested. Expect OpenVPN connections to flicker or die. Just use it to access controller server only. I never experienced any issues requiring intervention on test computers.
Best regards,
Simon
[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 2965 bytes --]
next prev parent reply other threads:[~2019-06-21 15:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-05 11:55 [Openvpn-devel] Community meetings in June 2019
2019-06-06 19:10 ` [Openvpn-devel] Summary of the community meeting (6th June 2019)
2019-06-12 10:16 ` [Openvpn-devel] Summary of the community meeting (12th "
2019-06-20 19:14 ` [Openvpn-devel] Summary of the community meeting (20th "
2019-06-21 15:59 ` Simon Rozman [this message]
2019-06-24 11:33 `
2019-06-24 18:13 `
2019-06-24 20:24 `
2019-06-25 8:55 `
2019-07-04 13:08 ` Simon Rozman
2019-07-05 9:04 `
2019-06-26 11:05 ` [Openvpn-devel] Summary of the community meeting (26th "
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=FF8443AE-D430-496D-881A-C75171649BA6@...2293... \
--to=unknown@example.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.