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:27:19 -0800	[thread overview]
Message-ID: <CALaUSutvXe-QSKa4V6+ZHR+r5aua6nUzh73LUygk2aDo1ffc1Q@mail.gmail.com> (raw)
In-Reply-To: <CAHmME9rZsWXeGh__RpuZSC9ycgeK+jQ6OhRaksqX5P+LpcmnyQ@mail.gmail.com>

My understanding is that in both cases the tunnels were left in a
deactivated state. Once activated the tunnels worked fine. Further
intervention wasn't needed.

On Tue, Nov 17, 2020 at 1:13 PM Jason A. Donenfeld <Jason@zx2c4.com> wrote:
>
> This part of your log:
>
> 2020-11-17 08:19:14.469253: [MGR] Migrated configuration from
> ‘C:\WINDOWS\system32\config\systemprofile\AppData\Local\WireGuard\Configurations\SCJ.conf.dpapi’
> to ‘C:\Program Files\WireGuard\Data\Configurations\SCJ.conf.dpapi’
> 2020-11-17 08:19:14.480225: [MGR] Migrated service command line
> arguments for ‘WireGuardTunnel$SCJ’
> 2020-11-17 08:19:14.485210: [MGR] Starting UI process for user
> ‘[REDACTED_PERSON_A]@SCJ’ for session 1
> 2020-11-17 08:19:14.509146: [TUN] Unable to load configuration from
> path: open C:\WINDOWS\system32\config\systemprofile\AppData\Local\WireGuard\Configurations\SCJ.conf.dpapi:
> The system cannot find the path specified.
> 2020-11-17 08:19:14.509146: [TUN] Shutting down
>
> Seems like it's do to a race in the migration, which this commit should fix:
> https://git.zx2c4.com/wireguard-windows/commit/?id=6e4e535e0c1108bbd5a3f15e273e13868f4ece20
>
> 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?
>
> Jason

  reply	other threads:[~2020-11-17 21:27 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 [this message]
2020-11-17 21:36     ` Jason A. Donenfeld
2020-11-17 21:44       ` Joshua Sjoding
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=CALaUSutvXe-QSKa4V6+ZHR+r5aua6nUzh73LUygk2aDo1ffc1Q@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).