From: Simon Rozman <simon@rozman.si>
To: Johnathan Clarke <johnathanclarke@gmail.com>,
"wireguard@lists.zx2c4.com" <wireguard@lists.zx2c4.com>
Subject: RE: Error when connecting from windows client
Date: Tue, 27 Apr 2021 09:54:15 +0000 [thread overview]
Message-ID: <8720b8df1b0d4226a4c93d056c9b0b97@rozman.si> (raw)
In-Reply-To: <CAOSAzkJJiv6uqVgdPqCYpGqabti3bmDrBU1gAX8Oy7ZqikuYNw@mail.gmail.com>
Hi,
> 2021-04-26 14:45:33.382398: [TUN] [Home] Creating Wintun interface
> 2021-04-26 14:45:33.519928: [TUN] [Home] [Wintun] CreateAdapter:
> Creating adapter
> 2021-04-26 14:45:33.828328: [TUN] [Home] [Wintun] SelectDriver: Using
> existing driver 0.10
> 2021-04-26 14:45:34.289159: [TUN] [Home] [Wintun] CreateAdapter:
> Failed to setup adapter (status: 0x0): The operation completed
> successfully. (Code 0x00000000)
Your log indicates that the adapter device was created, but has a problem code with a STATUS_SUCCESS problem status. I have reintroduced the problem code check in https://git.zx2c4.com/wintun/commit/?id=2881164bff0e819f6b0b6d5fc5d3a185ecb47457. This should evaluate the Wintun adapter state with better precision.
Meanwhile, can you please examine your C:\Windows\INF\setupapi.dev.log file for clues. (Note that a 0x1f/0xc0000495 problem code/status is normal when Wintun adapter is created early at boot. Hence the STATUS_PNP_DEVICE_CONFIGURATION_PENDING check in the code.)
Regards, Simon
next prev parent reply other threads:[~2021-04-27 9:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAOSAzkKgZS_-tRkbo10gZ3CrTfNPfBUuBUwY4bMY+W0Ynj_pNg@mail.gmail.com>
2021-04-26 5:34 ` Fwd: " Johnathan Clarke
2021-04-27 9:54 ` Simon Rozman [this message]
2021-04-28 21:29 ` Johnathan Clarke
2021-05-22 18:41 Hank Bao
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=8720b8df1b0d4226a4c93d056c9b0b97@rozman.si \
--to=simon@rozman.si \
--cc=johnathanclarke@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).