From: Aaron Jones <me@aaronmdjones.net>
To: wireguard@lists.zx2c4.com
Cc: Hendrik Friedel <hendrik@friedels.name>
Subject: Re: Better Output
Date: Sun, 17 Apr 2022 19:05:43 +0000 [thread overview]
Message-ID: <c93e4542-d4d8-8cef-871a-0c3810d3242f@aaronmdjones.net> (raw)
In-Reply-To: <em19dde1c0-bcda-4ad2-b3ce-d72fb64993e4@envy>
[-- Attachment #1.1: Type: text/plain, Size: 1152 bytes --]
On 17/04/2022 08:22, Hendrik Friedel wrote:
> I would suggest an improvement here:
>
> 1) If no Server responds on the particular domain/IP,
> wireguard should show a message
This would be technically achievable, but note that WireGuard
uses UDP, which has no concept of "connections". See also
below.
> 2) If a wireguard server responds, but the key is not valid
WireGuard does not respond if the keys are not valid. See
section 5.1 ("Silence is a Virtue") in the WireGuard
whitepaper [1].
> 3) If the connection fails, the Windows Client should show
> a RED symbol under status.
This could only be determined by a previously-in-use session
having had no packets received for greater than the maximum
rekey interval (2 minutes).
However, WireGuard itself will not send any data if it has no
data to send (same section of the whitepaper), and so if you
are not using the tunnel for 2 minutes, this would be
indistinguishable from a failed tunnel.
An exception is if you enable keepalives; they are 0-length
data packets.
[1] https://www.wireguard.com/papers/wireguard.pdf
Regards,
Aaron Jones
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2022-04-17 19:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-17 8:22 Hendrik Friedel
2022-04-17 19:05 ` Aaron Jones [this message]
2022-04-18 8:40 ` Re[2]: " Hendrik Friedel
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=c93e4542-d4d8-8cef-871a-0c3810d3242f@aaronmdjones.net \
--to=me@aaronmdjones.net \
--cc=hendrik@friedels.name \
--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).