From: "Hendrik Friedel" <email@example.com> To: "Jason A. Donenfeld" <Jason@zx2c4.com>, "WireGuard mailing list" <firstname.lastname@example.org> Subject: Re: [ANNOUNCE] WireGuardNT, a high-performance WireGuard implementation for the Windows kernel Date: Fri, 13 Aug 2021 15:58:18 +0000 [thread overview] Message-ID: <emf58fb568-663d-469b-aa45-48fbf11e46b4@envy> (raw) In-Reply-To: <CAHmME9p8WLAzd=W+Z6MKtke5PYb_T6iMbvBFirmCeUQzxycRwQ@mail.gmail.com> Hello Jason, thanks for your work on Wireguard. I have just updated and activated the experimental driver. The fact that I do not need to activate it in the registry was decisive for me ;-) I cannot report any issue so far. Best regards, Hendrik ------ Originalnachricht ------ Von: "Jason A. Donenfeld" <Jason@zx2c4.com> An: "WireGuard mailing list" <email@example.com> Gesendet: 13.08.2021 13:52:39 Betreff: Re: [ANNOUNCE] WireGuardNT, a high-performance WireGuard implementation for the Windows kernel >Hi everyone, > >On Mon, Aug 2, 2021 at 7:28 PM Jason A. Donenfeld <Jason@zx2c4.com> wrote: >> Nonetheless, experimental or not, we still need people to test this and help >> shake out issues. To that end, WireGuardNT is now available in the ordinary >> WireGuard for Windows client -- https://www.wireguard.com/install/ -- with the >> 0.4.z series, in addition to having full support of the venerable wg(8) >> utility, but currently (August 2021; if you're reading this in the future this >> might not apply) it is behind a manually set registry knob. There will be >> three phases of the 0.4.z series: >> >> Phase 1) WireGuardNT is hidden behind the "ExperimentalKernelDriver" >> registry knob. If you don't manually tinker around to enable it, >> the client will continue to use wireguard-go/Wintun like before. > >After the first few days, bug reports for WireGuardNT have died down >considerably. It's hard to tell whether that's a sign that the >software is stable or that nobody is using it. So, we're still in >phase 1. However, with version 0.4.5 of the client, I've added a >checkbox below the "activate" button in order to make the experimental >testing more discoverable. I dislike such knobs, but I'd rather have >more testing than less, before turning it on by default. Hopefully >this will make it easier for alpha testers to give it a spin and >report findings. If you have been testing the driver, and it's been >working well for you, please write in to say so, simply as a signal >that it is being tested. If things stay as quiet as they are now on >the bug reporting front, we'll likely move into phase 2 -- enabling >WireGuardNT by default, with a registry key to revert to the legacy >implementation -- in 2 to 3 weeks. > >Jason
next prev parent reply other threads:[~2021-08-13 15:58 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-08-02 17:27 Jason A. Donenfeld 2021-08-13 11:52 ` Jason A. Donenfeld 2021-08-13 15:58 ` Hendrik Friedel [this message] 2021-08-13 16:09 ` Peter Whisker 2021-08-14 11:03 ` Phillip McMahon 2021-08-14 21:37 ` Morten Christensen 2021-08-16 8:15 ` nomad 2021-09-09 11:41 ` Jason A. Donenfeld 2021-09-12 21:06 ` Jason A. Donenfeld 2021-09-12 21:54 ` Jeffrey Walton 2021-09-18 0:27 ` Jason A. Donenfeld 2021-10-17 5:08 ` Jason A. Donenfeld
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=emf58fb568-663d-469b-aa45-48fbf11e46b4@envy \ --firstname.lastname@example.org \ --cc=Jason@zx2c4.com \ --email@example.com \ --subject='Re: Re: [ANNOUNCE] WireGuardNT, a high-performance WireGuard implementation for the Windows kernel' \ /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
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).