Development discussion of WireGuard
 help / color / mirror / Atom feed
* Wireguard Windows ARM64 Build 21327
@ 2021-03-05 20:29 Bradley Saulteaux
  2021-03-07 15:49 ` Jason A. Donenfeld
  0 siblings, 1 reply; 8+ messages in thread
From: Bradley Saulteaux @ 2021-03-05 20:29 UTC (permalink / raw)
  To: wireguard

A quick FYI Wireguard UI stops launching in Windows ARM64 Build 21327. Version 0.3.5 works for me as a temporary workaround. I'm not expecting my configuration to be supported or stressed over in the slightest. I just want to let everyone know about it in case the issue finds its way into official builds.


^ permalink raw reply	[flat|nested] 8+ messages in thread

* Re: Wireguard Windows ARM64 Build 21327
  2021-03-05 20:29 Wireguard Windows ARM64 Build 21327 Bradley Saulteaux
@ 2021-03-07 15:49 ` Jason A. Donenfeld
  2021-03-08  9:25   ` Bradley Saulteaux
  0 siblings, 1 reply; 8+ messages in thread
From: Jason A. Donenfeld @ 2021-03-07 15:49 UTC (permalink / raw)
  To: Bradley Saulteaux; +Cc: wireguard

Hi Bradley,

Thanks for the report.

> I'm not expecting my configuration to be supported or stressed over in the slightest.

You are in fact very mistaken here. Having everything be broken and
requiring you to resort to out of date versions is very much something
that I'll stress over. Let's fix this.

The first thing I'm wondering is:
- Did v0.3.8 work in builds prior to 21327, or did you never get a
chance to test v0.3.8 on other builds?

Jason

^ permalink raw reply	[flat|nested] 8+ messages in thread

* Re: Wireguard Windows ARM64 Build 21327
  2021-03-07 15:49 ` Jason A. Donenfeld
@ 2021-03-08  9:25   ` Bradley Saulteaux
  2021-03-08 15:00     ` Jason A. Donenfeld
  0 siblings, 1 reply; 8+ messages in thread
From: Bradley Saulteaux @ 2021-03-08  9:25 UTC (permalink / raw)
  To: Jason A. Donenfeld; +Cc: wireguard

Hello Jason,

Yes prior to build 21327 the latest version worked.


‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Sunday, March 7, 2021 8:49 AM, Jason A. Donenfeld <Jason@zx2c4.com> wrote:

> Hi Bradley,
>
> Thanks for the report.
>
> > I'm not expecting my configuration to be supported or stressed over in the slightest.
>
> You are in fact very mistaken here. Having everything be broken and
> requiring you to resort to out of date versions is very much something
> that I'll stress over. Let's fix this.
>
> The first thing I'm wondering is:
>
> -   Did v0.3.8 work in builds prior to 21327, or did you never get a
>     chance to test v0.3.8 on other builds?
>
>     Jason
>



^ permalink raw reply	[flat|nested] 8+ messages in thread

* Re: Wireguard Windows ARM64 Build 21327
  2021-03-08  9:25   ` Bradley Saulteaux
@ 2021-03-08 15:00     ` Jason A. Donenfeld
  2021-03-20  2:33       ` Jason A. Donenfeld
  0 siblings, 1 reply; 8+ messages in thread
From: Jason A. Donenfeld @ 2021-03-08 15:00 UTC (permalink / raw)
  To: Bradley Saulteaux; +Cc: wireguard

On Mon, Mar 8, 2021 at 2:25 AM Bradley Saulteaux
<bradsoto@protonmail.com> wrote:
>
> Hello Jason,
>
> Yes prior to build 21327 the latest version worked.

Hmm. Anything in the logs from the flawed 0.3.8 launches that might
indicate something?

If you're up for debugging this in real time with me, perhaps we can
jump onto IRC and I can send a few tweaked builds? I'm zx2c4 on
freenode.

Jason

^ permalink raw reply	[flat|nested] 8+ messages in thread

* Re: Wireguard Windows ARM64 Build 21327
  2021-03-08 15:00     ` Jason A. Donenfeld
@ 2021-03-20  2:33       ` Jason A. Donenfeld
  2021-03-20  5:39         ` Bradley Saulteaux
  0 siblings, 1 reply; 8+ messages in thread
From: Jason A. Donenfeld @ 2021-03-20  2:33 UTC (permalink / raw)
  To: Bradley Saulteaux; +Cc: wireguard

Hi Bradley,

The hardware I ordered finally came and I was able to reproduce and
then fix the bug, which was in the Go runtime.

The bug report I filed is here: https://github.com/golang/go/issues/45138

As of writing, the fix I've submitted is here:
https://go-review.googlesource.com/c/go/+/303273/
But that fix could wind up being wrong and replaced with something
else. Either way, as soon as that or something else is merged, I'll
cut a new release with the fix in it.

Thanks again for the report.

Regards,
Jason

^ permalink raw reply	[flat|nested] 8+ messages in thread

* Re: Wireguard Windows ARM64 Build 21327
  2021-03-20  2:33       ` Jason A. Donenfeld
@ 2021-03-20  5:39         ` Bradley Saulteaux
  2021-03-23  2:32           ` Jason A. Donenfeld
  0 siblings, 1 reply; 8+ messages in thread
From: Bradley Saulteaux @ 2021-03-20  5:39 UTC (permalink / raw)
  To: Jason A. Donenfeld; +Cc: wireguard

Thank you very much!

‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Friday, March 19, 2021 8:33 PM, Jason A. Donenfeld <Jason@zx2c4.com> wrote:

> Hi Bradley,
>
> The hardware I ordered finally came and I was able to reproduce and
> then fix the bug, which was in the Go runtime.
>
> The bug report I filed is here: https://github.com/golang/go/issues/45138
>
> As of writing, the fix I've submitted is here:
> https://go-review.googlesource.com/c/go/+/303273/
> But that fix could wind up being wrong and replaced with something
> else. Either way, as soon as that or something else is merged, I'll
> cut a new release with the fix in it.
>
> Thanks again for the report.
>
> Regards,
> Jason



^ permalink raw reply	[flat|nested] 8+ messages in thread

* Re: Wireguard Windows ARM64 Build 21327
  2021-03-20  5:39         ` Bradley Saulteaux
@ 2021-03-23  2:32           ` Jason A. Donenfeld
  2021-03-23 22:21             ` Bradley Saulteaux
  0 siblings, 1 reply; 8+ messages in thread
From: Jason A. Donenfeld @ 2021-03-23  2:32 UTC (permalink / raw)
  To: Bradley Saulteaux; +Cc: wireguard

Hi again Bradley,

https://github.com/golang/go/commit/78afca22c9485dbd44da3b909866bbb9c1eaf440
was committed, and so WireGuard for Windows v0.3.9 was released. You
said that you downgraded to some earlier arm32 version, so I imagine
you've just been ignoring the update notification. Try updating now,
and see if things go well.

Jason

^ permalink raw reply	[flat|nested] 8+ messages in thread

* Re: Wireguard Windows ARM64 Build 21327
  2021-03-23  2:32           ` Jason A. Donenfeld
@ 2021-03-23 22:21             ` Bradley Saulteaux
  0 siblings, 0 replies; 8+ messages in thread
From: Bradley Saulteaux @ 2021-03-23 22:21 UTC (permalink / raw)
  To: Jason A. Donenfeld; +Cc: wireguard

Brilliant! It works better than ever. The world needs more people like you sir, you do fantastic work. Thank you so much.


‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Monday, March 22, 2021 8:32 PM, Jason A. Donenfeld <Jason@zx2c4.com> wrote:

> Hi again Bradley,
>
> https://github.com/golang/go/commit/78afca22c9485dbd44da3b909866bbb9c1eaf440
> was committed, and so WireGuard for Windows v0.3.9 was released. You
> said that you downgraded to some earlier arm32 version, so I imagine
> you've just been ignoring the update notification. Try updating now,
> and see if things go well.
>
> Jason



^ permalink raw reply	[flat|nested] 8+ messages in thread

end of thread, other threads:[~2021-03-23 22:24 UTC | newest]

Thread overview: 8+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2021-03-05 20:29 Wireguard Windows ARM64 Build 21327 Bradley Saulteaux
2021-03-07 15:49 ` Jason A. Donenfeld
2021-03-08  9:25   ` Bradley Saulteaux
2021-03-08 15:00     ` Jason A. Donenfeld
2021-03-20  2:33       ` Jason A. Donenfeld
2021-03-20  5:39         ` Bradley Saulteaux
2021-03-23  2:32           ` Jason A. Donenfeld
2021-03-23 22:21             ` Bradley Saulteaux

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).