From: Simon Rozman <simon@rozman.si>
To: Manikandan Thiagarajan <tmani@prosimo.io>,
"wireguard@lists.zx2c4.com" <wireguard@lists.zx2c4.com>
Subject: RE: Windows Tunnl.dll fails to start as a service.
Date: Mon, 25 Jan 2021 08:10:03 +0000 [thread overview]
Message-ID: <42d43d1503f34b8c87acda5fdf50307c@rozman.si> (raw)
In-Reply-To: <CAJV1VRBLdBwD=bud-M7LmcFUiHfHdNa3iNbBFzJzj+4GNpPSRQ@mail.gmail.com>
Hi,
> Log Name: System
> Source: Service Control Manager
> Date: 1/21/2021 9:41:25 AM
> Event ID: 7024
> Task Category: None
> Level: Error
> Keywords: Classic
> User: N/A
> Computer: MANI-WIN10-TEST
> Description:
> The ProsimoTunnel_if_cbc2a056dfdc25f7 service terminated with the
> following service-specific error:
> The system cannot find the path specified.
"The system cannot find the path specified." <= is your service path correct? Double check it. Mind the path deflection for WoW64 processes. SCM is always native (x64 on x64 Windows, x86 on x86 Windows...). So, the service path must match the path as a native process would see it.
Or is it just the fact that something returns status 2 which is interpreted as ERROR_FILE_NOT_FOUND by the Event Log?
> 2021-01-21 10:04:20.181831: [TUN] [if_1ea7d00c23a616b1] Creating Wintun
> interface
> 2021-01-21 10:04:20.896480: [TUN] [if_1ea7d00c23a616b1] Using
> Wintun/0.8 (NDIS 6.83)
> 2021-01-21 10:04:20.909065: [TUN] [if_1ea7d00c23a616b1] Enabling
> firewall rules
> 2021-01-21 10:04:22.126556: [TUN] [if_1ea7d00c23a616b1] Starting
> WireGuard/0.1.1 (Windows 10.0.19041; amd64)
> 2021-01-21 10:04:22.127580: [TUN] [if_1ea7d00c23a616b1] Watching network
> interfaces
> 2021-01-21 10:04:22.128604: [TUN] [if_1ea7d00c23a616b1] Resolving DNS
> names
> 2021-01-21 10:04:22.135234: [TUN] [if_1ea7d00c23a616b1] Creating Wintun
> interface
> 2021-01-21 10:04:24.156638: [TUN] [if_1ea7d00c23a616b1] Starting
> WireGuard/0.1.1 (Windows 10.0.19041; amd64)
> 2021-01-21 10:04:24.159365: [TUN] [if_1ea7d00c23a616b1] Watching network
> interfaces
> 2021-01-21 10:04:24.159365: [TUN] [if_1ea7d00c23a616b1] Resolving DNS
> names
> 2021-01-21 10:04:24.165375: [TUN] [if_1ea7d00c23a616b1] Creating Wintun
> interface
> 2021-01-21 10:04:24.616820: [TUN] [if_1ea7d00c23a616b1] Unable to create
> Wintun interface: Error registering rings: Error listing NDIS
> interfaces: no interfaces found
Wintun 0.8 is out of our support. Please, upgrade your wireguard-go and Wintun to the latest version first and see if the problem persists.
Why is that important? Because, we completely rewrote the wireguard-go <-> Wintun communication in v0.0.20201118 and v0.10 respectively. The issue you are seeing is triggered in a part of the code that is now gone from wireguard-go and has been rewritten in the new wintun.dll.
(The new Wintun no longer ships as a driver package you need to install, but rather as a self-contained do-it-all DLL. Don't worry, the new wireguard-go knows how to use it. Just add wintun.dll next to it.)
Regards,
Simon
next prev parent reply other threads:[~2021-01-25 8:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-21 18:38 Manikandan Thiagarajan
2021-01-25 8:10 ` Simon Rozman [this message]
2021-01-26 21:55 ` Manikandan Thiagarajan
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=42d43d1503f34b8c87acda5fdf50307c@rozman.si \
--to=simon@rozman.si \
--cc=tmani@prosimo.io \
--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).