From: Simon Rozman <simon@rozman.si>
To: Mark Nichols <mnichols62@yahoo.com>,
"wireguard@lists.zx2c4.com" <wireguard@lists.zx2c4.com>
Subject: RE: Unable to create Wintun Interface
Date: Thu, 12 Dec 2019 09:53:12 +0000 [thread overview]
Message-ID: <99D61A626FDA8A4B90A270669121BE10D0597B0D@PLANJAVA.amebis.doma> (raw)
In-Reply-To: <860712054.4029860.1574276656913@mail.yahoo.com>
[-- Attachment #1.1.1: Type: text/plain, Size: 1954 bytes --]
Please check if you have any network adapter that has a name similar to the
tunnel name you are trying to use (Control Panel\Network and Internet\Network
Connections). WireGuard needs to have a network adapter with the name that
corresponds to the tunnel name. In your case, it fails naming it.
Maybe you named your Ethernet/Wifi adapter as "MyCompany", and then created a
WireGuard tunnel with the same name "MyCompany". Maybe you have a WiFi SSID
named "MyCompany". Try picking different name for your WireGuard tunnel. Other
than WireGuard tunnel and adapter names must be aligned internal limitation,
the name of the tunnel doesn't play any significant role. You can select a
different name (e.g. "MyCompanyWG", "wg0", etc.) and try again.
Best regards,
Simon
From: WireGuard <wireguard-bounces@lists.zx2c4.com> On Behalf Of Mark Nichols
Sent: Wednesday, November 20, 2019 8:04 PM
To: wireguard@lists.zx2c4.com
Subject: Unable to create Wintun Interface
I've just installed Wireguard on Windows 10 64-bit using the msi installer.
When I create a tunnel and try to connect, I get:
Unable to create Wintun interface: Error creating interface: Unable to set
name of Wintun interface: NciSetConnectionName failed: The requested operation
was made in the context of a transaction that is no longer active.
I have uninstalled and reinstalled from the command prompt as the
administrator.
I have validated the tunnel works with the configured parameters on a Mac.
Any suggestions?
Mark Nichols
Discrimination, oppression, and injustice are challenges to be overcome, tools
to sharpen our determination, and reflections on the poor character of the
oppressor. Lack of opportunity is a calling to create something new and
better. If we choose to see circumstances as something to overcome on our way
to success instead of allowing them to define us as a victim, we retain the
power to pursue our highest destiny.
[-- Attachment #1.1.2: Type: text/html, Size: 6562 bytes --]
[-- Attachment #1.2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 4919 bytes --]
[-- Attachment #2: Type: text/plain, Size: 148 bytes --]
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard
prev parent reply other threads:[~2019-12-12 9:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <860712054.4029860.1574276656913.ref@mail.yahoo.com>
2019-11-20 19:04 ` Mark Nichols
2019-12-12 9:53 ` Simon Rozman [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=99D61A626FDA8A4B90A270669121BE10D0597B0D@PLANJAVA.amebis.doma \
--to=simon@rozman.si \
--cc=mnichols62@yahoo.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).