From: Jan Petrischkeit <jan.petrischkeit@hochschule-stralsund.de>
To: Simon Rozman <simon@rozman.si>,
"wireguard@lists.zx2c4.com" <wireguard@lists.zx2c4.com>
Subject: Re: wireguard-windows: Wireguard does not start a previously activated tunnel from time to time
Date: Thu, 29 Sep 2022 07:43:45 +0200 [thread overview]
Message-ID: <3a27c871-f150-44fe-6d29-d5191be6cf79@hochschule-stralsund.de> (raw)
In-Reply-To: <03b8866a0f8249c8883d9a0244ddea1b@rozman.si>
[-- Attachment #1: Type: text/plain, Size: 1687 bytes --]
Hi,
thank you for this information, I will take a look at that. Now I know
where to look.
However, I am using the "endpoint-by-dns" for a specific reason:
In my area there is an internet provider which uses carrier grade nat in
a strange way, so that no rdp session can be created over a wireguard
tunnel if the ipv4 address of the server is used as endpoint. I created
a dns entry for the wireguard server, so that in these cases the ipv6
address is used and the tunnel is established without the weird nat of
the internet provider in between.
Since not all people here have activated ipv6 in their home routers or
have always an ipv6 connection while traveling, I cannot simply use the
ipv6 adress in the config.
Regards,
Jan
Am 28.09.22 um 19:23 schrieb Simon Rozman:
> Hi,
>
>> Event 7023, ServiceControlManager: The service "WireGuardTunnel$HOST-
>> WG2" was terminated with the following error: The requested name is valid,
>> but no data of the requested type was found.
>
> The error message you are mentioning is WSANO_DATA 11004 which is related to DNS resolution problems. Which is kind of expected early in the boot process when the Dnscache service is starting and/or Dhcp service might not yet configured the DNS.
>
> I presume changing the Endpoint= lines of peers to contain IPs rather than hostnames could solve your problem.
>
> See if it helps.
>
> If you can confirm it, maybe we can add some retry on WSANO_DATA in the wireguard-windows. (Personally, I would avoid adding hard dependency on Dnscache and Dhcp services. As there are situations where they can be disabled, preventing the WireGuard tunnel service startup then.)
>
> Regards,
> Simon
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 5386 bytes --]
prev parent reply other threads:[~2022-09-29 5:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-20 13:16 Jan Petrischkeit
2022-09-28 17:23 ` Simon Rozman
2022-09-29 5:43 ` Jan Petrischkeit [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=3a27c871-f150-44fe-6d29-d5191be6cf79@hochschule-stralsund.de \
--to=jan.petrischkeit@hochschule-stralsund.de \
--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).