Development discussion of WireGuard
 help / color / mirror / Atom feed
From: Ferad Zyulkyarov <feradz@gmail.com>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>,
	Simon Rozman <simon@rozman.si>
Subject: Re: WireGuard on Windows: Unable to create Wintun interface: Error registering rings: Error listing NDIS interfaces: no interfaces found
Date: Tue, 18 Aug 2020 10:50:49 +0200	[thread overview]
Message-ID: <CAARAvpLXrRummZrkG8g2xS97SeiBDC_ZC9+iygX0V8P_kokpUQ@mail.gmail.com> (raw)
In-Reply-To: <CAHmME9qobq9ZhyOGm5WaTTXA0i=k=_w0L+7LWCPcjUye5idJYA@mail.gmail.com>

Jason and Simon, thanks for the reply.

I tried Jason's recommendation and added Tcpip as a dependence to the
WireGuard service. This doesn't seem to solve the problem.

I added the dependency by executing the following command:
sc config WireGuardTunnel$wg0 depend= nsi/Tcpip

After executing this command I verified that noth NSI and TCPIP are
listed as dependencies.

I restarted the machine few times but still WireGuard does not start
automatically when the machine starts.There is the same error in the
WireGuard log file: [tun] [wg0] Unable to create Wintun interface:
Error registering
rings: Error listing NDIS interfaces: no interfaces found

I need to start WireGuard manually.

I tried the recommendation from Simon to set startup type to
"Automatic (delayed start)" for the WireGuard service. Unfortunately,
this also does not solve the problem. WireGuard does not start. I
check the logs and I see

[MGR] Removing Wintun interface ‘wg0’ because its service is stopped

It looks like the WireGuard manager removes the service and installs
again. As a result the dependency to TCPIP disappears.

In my first email I explained, but worth mentioning again. There are
other Windows machines same OS, where WireGuard starts automatically
at startup. This is very strange that in some machines it starts and
in others it does not. If you guide me I can try to help debug this
issue and address.

Regards,
Ferad


On Tue, Aug 18, 2020 at 9:43 AM Jason A. Donenfeld <Jason@zx2c4.com> wrote:
>
> Hopefully this addresses your issue:
> https://git.zx2c4.com/wireguard-windows/commit/?id=86cf5c84384bde2b4147fc5eedee24937729a101

      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
2020-08-18  7:43 ` Jason A. Donenfeld
2020-08-18  8:50   ` Ferad Zyulkyarov [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=CAARAvpLXrRummZrkG8g2xS97SeiBDC_ZC9+iygX0V8P_kokpUQ@mail.gmail.com \
    --to=feradz@gmail.com \
    --cc=Jason@zx2c4.com \
    --cc=simon@rozman.si \
    --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).