From: matt spaethe <mspaethe@outlook.com>
To: "wireguard@lists.zx2c4.com" <wireguard@lists.zx2c4.com>
Subject: wireguard command line, dumplog and GUI pop-up in 0.3.16
Date: Fri, 9 Jul 2021 05:48:07 +0000 [thread overview]
Message-ID: <DS7PR07MB759127E1827ED9A3CBB69D43CF189@DS7PR07MB7591.namprd07.prod.outlook.com> (raw)
In-Reply-To: <DS7PR07MB7591F166B9EC0B30DB10D5B0CF189@DS7PR07MB7591.namprd07.prod.outlook.com>
Hi,
I installed wireguard 0.3.16 as a tunnel on Windows 10 IoT. When I attempt to dump the log buffer to file, I get a pop up about usage of wireguard command line. I then verified that I can still perform /dumplog on a second machine with 0.3.14.
I then went to a third machine with 0.3.14 and /dumplog worked successfully. I then upgraded to 0.3.16 from inside WireGuard Manager on this machine. In the same Windows shell, the command 'wireguard /dumplog log.txt' results in a pop up about command line usage.
I've been trying to run without Manager because I don't want users accidently shutting down the wireguard tunnel. So to look at logs, I use the command line option /dumplog.
Thank you,
Matt
next parent reply other threads:[~2021-08-02 13:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <DS7PR07MB7591F166B9EC0B30DB10D5B0CF189@DS7PR07MB7591.namprd07.prod.outlook.com>
2021-07-09 5:48 ` matt spaethe [this message]
2021-08-02 14:02 ` 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=DS7PR07MB759127E1827ED9A3CBB69D43CF189@DS7PR07MB7591.namprd07.prod.outlook.com \
--to=mspaethe@outlook.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).