From: David Woodhouse <dwmw2@infradead.org>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>,
Daniel Lenski <dlenski@gmail.com>
Subject: Re: Duplicate IP address, and permissions problems on Windows
Date: Wed, 07 Apr 2021 09:18:25 +0100 [thread overview]
Message-ID: <e8f0a880ccdca6b252a5b45ebdc54f83ee3fae57.camel@infradead.org> (raw)
In-Reply-To: <CAHmME9q-qw=sCxz6Fije+ENQTY2-GdS4bZLSakuh+6Eze4LR3w@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1159 bytes --]
On Tue, 2021-04-06 at 18:17 -0600, Jason A. Donenfeld wrote:
> It's pretty typical behavior on Windows for IP addresses to be
> exclusive per interface. WireGuard for Windows does something similar:
> https://git.zx2c4.com/wireguard-windows/tree/tunnel/addressconfig.go#n22
Thanks. That seems to run cleanupAddressesOnDisconnectedInterfaces()
only if the original SetIPAddressesForFamily() call return
ERROR_OBJECT_ALREADY_EXISTS, while I was fairly sure that in my case
the CreateUnicastIpAddressEntry() call was succeeding. I'll go and
experiment with it some more.
> With regards to permissions, you must be Local System, which is
> already the case if you're running inside a service. If you'd like to
> run as a mere Administrator process, you can steal a token with a
> technique like https://git.zx2c4.com/wireguard-tools/tree/src/ipc-uapi-windows.h#n14
> or https://git.zx2c4.com/wireguard-windows/tree/elevate/doas.go#n30
Great, thanks!
Is there a list of precisely which operations require such privileges?
Is it only *creating* an adapter? Or only if doing so requires the
kernel driver to be loaded for the first time?
[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 5174 bytes --]
next prev parent reply other threads:[~2021-04-07 8:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-06 11:29 Duplicate IP address, and permissions problems on Windows David Woodhouse
2021-04-07 0:17 ` Jason A. Donenfeld
2021-04-07 8:18 ` David Woodhouse [this message]
2021-04-07 23:05 ` Daniel Lenski
2021-04-12 17:50 ` Jason A. Donenfeld
2021-04-07 23:00 ` Daniel Lenski
2021-04-08 8:46 ` David Woodhouse
2021-04-08 16:09 ` Daniel Lenski
2021-04-08 16:59 ` David Woodhouse
2021-04-08 17:53 ` Daniel Lenski
2021-04-10 9:25 ` David Woodhouse
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=e8f0a880ccdca6b252a5b45ebdc54f83ee3fae57.camel@infradead.org \
--to=dwmw2@infradead.org \
--cc=Jason@zx2c4.com \
--cc=dlenski@gmail.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).