Development discussion of WireGuard
 help / color / mirror / Atom feed
From: Joshua Sjoding <joshua.sjoding@scjalliance.com>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: WireGuard for Windows fails to enable firewall rules after update to v0.2.1
Date: Tue, 17 Nov 2020 13:44:39 -0800	[thread overview]
Message-ID: <CALaUSusVyLRWKh93U3+Szdrf5LbiOnB+QiXaZPG=9ESekTrpvQ@mail.gmail.com> (raw)
In-Reply-To: <CAHmME9qOumhK+LxadUOw1TmD0NRg9+qvOhmFsGSFbC0w3jX2mA@mail.gmail.com>

Magnificent!

We'll hold off on further updates until the new release is ready. If
we run into any issues with it we'll let you know.

And thank you so much Jason for all that you do. We appreciate your
tireless efforts!

Joshua Sjoding
SCJ Alliance
IT Specialist
www.scjalliance.com

On Tue, Nov 17, 2020 at 1:36 PM Jason A. Donenfeld <Jason@zx2c4.com> wrote:
>
> On Tue, Nov 17, 2020 at 10:13 PM Jason A. Donenfeld <Jason@zx2c4.com> wrote:
> > But this part of your log:
> >
> > 2020-11-17 08:19:29.582424: [TUN] [SCJ] Enabling firewall rules
> > 2020-11-17 08:19:29.746988: [TUN] [SCJ] Unable to enable firewall
> > rules: Firewall error at
> > golang.zx2c4.com/wireguard/windows/tunnel/firewall/helpers.go:100: The
> > specified group does not exist.
> > 2020-11-17 08:19:29.767930: [TUN] [SCJ] Shutting down
> >
> > Is extremely puzzling. I'm wondering what led to this and how you
> > eventually appeared to fix it. Did it go away on its own without user
> > intervention? Did you have to manually start/stop the tunnel a few
> > times?
>
> I've now triaged and fixed this issue. It was a problem in Go's
> x/sys/windows library, which I've fixed upstream here:
> https://go-review.googlesource.com/c/sys/+/270897
>
> This should hopefully land soon, and I'll likely cut another release
> to address this. I don't like taking down people's tunnels like this.
>
> Thanks a lot for these logs and reports. I believe both of the issues
> in this email thread are resolved.
>
> Jason

  reply	other threads:[~2020-11-17 21:45 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-17 18:43 Joshua Sjoding
2020-11-17 20:59 ` Jason A. Donenfeld
2020-11-17 21:13   ` Jason A. Donenfeld
2020-11-17 21:27     ` Joshua Sjoding
2020-11-17 21:36     ` Jason A. Donenfeld
2020-11-17 21:44       ` Joshua Sjoding [this message]
2020-11-17 22:29       ` 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='CALaUSusVyLRWKh93U3+Szdrf5LbiOnB+QiXaZPG=9ESekTrpvQ@mail.gmail.com' \
    --to=joshua.sjoding@scjalliance.com \
    --cc=Jason@zx2c4.com \
    --cc=wireguard@lists.zx2c4.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 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).