Development discussion of WireGuard
 help / color / mirror / Atom feed
From: "Hendrik Friedel" <hendrik@friedels.name>
To: wireguard@lists.zx2c4.com
Subject: Better Output
Date: Sun, 17 Apr 2022 08:22:32 +0000	[thread overview]
Message-ID: <em19dde1c0-bcda-4ad2-b3ce-d72fb64993e4@envy> (raw)

Hello,

when using wireguard - both Android and Windows - clients, I in the past 
often thought that the connection is fine but in fact, I had a wrong 
Key.
The Windows-Client showed a green Checkmark under Status. The Android 
Client showed the "key" symbol and it showed also the "switch" on the 
right hand side (=activ) and blue.
Obviously, the connection was not working, but I would have hoped that 
Wireguard would have told me, that the connection was not ok.
In fact, I was only able to determine whether the connection was working 
by trying to access some Service (e.g. google) or by observing the 
"Received/bytes" counter which remained at 0.

I would suggest an improvement here:
1) If no Server responds on the particular domain/IP, wireguard should 
show a message
     Could not connect to [my.domain.com] under IP 
[2a00:1234:1234:c700:ba27:ebff:fe3e:2342] or 1.4.4.1.
2) If a wireguard server responds, but the key is not valid it should 
show a message
     Connection failed. Host responded, but key was invalid
3) If the connection fails, the Windows Client should show a RED symbol 
under status.
4) If the connection fails, the "key" symbol should not be shown under 
Android and the toggle-switch should move from right&blue (active) back 
to left&grey.

Would that be possible?

Greetings,
Hendrik


             reply	other threads:[~2022-04-17  8:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-17  8:22 Hendrik Friedel [this message]
2022-04-17 19:05 ` Aaron Jones
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=em19dde1c0-bcda-4ad2-b3ce-d72fb64993e4@envy \
    --to=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).