From: Simon Rozman <simon@rozman.si>
To: Ferad Zyulkyarov <feradz@gmail.com>,
"wireguard@lists.zx2c4.com" <wireguard@lists.zx2c4.com>
Subject: RE: WireGuard on Windows: Unable to create Wintun interface: Error registering rings: Error listing NDIS interfaces: no interfaces found
Date: Fri, 14 Aug 2020 10:00:56 +0000 [thread overview]
Message-ID: <99D61A626FDA8A4B90A270669121BE10D0DF5C6F@PLANJAVA.amebis.doma> (raw)
In-Reply-To: <CAARAvpL1PDSm5T_5pE5qUP9b+bMeUi9Td57op9t+OoSLvo9L2A@mail.gmail.com>
Hi,
> I have installed WireGuard on Windows server 2017. When I manually
> activate the tunnel through the client application (manager) all works
> fine. After I restart the computer, WireGuard fails to start
> automatically. The log contains the following error:
>
> [tun] [wg0] Unable to create Wintun interface: Error registering
> rings: Error listing NDIS interfaces: no interfaces found
>
> I can explicitly/manually activate the tunnel through the client
> application but I need the tunnel to start automatically if the machine
> restarts.
>
> I have it installed in other Windows Server 2017 machines and on those
> machines WireGuard starts automatically when the system boots.
>
> I would appreciate your help in addressing the problem of WireGuard auto
> start when the machine boots.
Looks like the WireGuard tunnel service is started too early on this particular computer - even before Windows networking (NDIS).
We need to investigate, which additional service or resource we need to make the Wireguard tunnel services depend on.
I would suggest you to change the WireGuard Manager and Tunnel services startup to Automatic (Delayed), but I am afraid the WireGuard Manager service deletes the tunnel services on each shutdown and recreates them on startup.
Furthermore, delayed-started services come up way after the Group Policy Client service. If you use WireGuard to remotely connect this computer to your Active Directory, the boot-time Group Policies won't apply.
So, anyway you slice it... we need to fix this in WireGuard service dependencies (or add a retry loop on boot as a last resort). Stay tuned.
Regards,
Simon
next prev parent reply other threads:[~2020-08-18 11:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-08 11:44 Ferad Zyulkyarov
2020-08-14 10:00 ` Simon Rozman [this message]
2020-08-18 7:43 ` Jason A. Donenfeld
2020-08-18 8:50 ` Ferad Zyulkyarov
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=99D61A626FDA8A4B90A270669121BE10D0DF5C6F@PLANJAVA.amebis.doma \
--to=simon@rozman.si \
--cc=feradz@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).