From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: Joshua Sjoding <joshua.sjoding@scjalliance.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 23:29:30 +0100 [thread overview]
Message-ID: <CAHmME9oJze5Pmf5SnRXaTtpYa2UWuCs7pdki2Qsp-yAewmwJaw@mail.gmail.com> (raw)
In-Reply-To: <CAHmME9qOumhK+LxadUOw1TmD0NRg9+qvOhmFsGSFbC0w3jX2mA@mail.gmail.com>
On Tue, Nov 17, 2020 at 10: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
Merged as:
https://github.com/golang/sys/commit/ba5294a509c715d7fea0f9022a3d0ca21f64942a
and updated in wireguard-windows here:
https://git.zx2c4.com/wireguard-windows/commit/?id=4cd498b8075e85e54711a0cf8481b9c74841d0ac
prev parent reply other threads:[~2020-11-17 22:30 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
2020-11-17 22:29 ` Jason A. Donenfeld [this message]
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=CAHmME9oJze5Pmf5SnRXaTtpYa2UWuCs7pdki2Qsp-yAewmwJaw@mail.gmail.com \
--to=jason@zx2c4.com \
--cc=joshua.sjoding@scjalliance.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).