From: Bzzzz <lazyvirus@gmx.com>
To: wireguard@lists.zx2c4.com
Subject: Doc enhancement
Date: Tue, 2 May 2017 16:51:45 +0200 [thread overview]
Message-ID: <20170502165145.2bf33eef@msi.defcon1> (raw)
Hi maillisters,
my concern is about the site's doc.
I spent a lot of time before getting the configuration files right
because of a small lack in the doc:
it is missing a few lines explaining that what's appears a "weird"
network notation has in fact 2 purposes, setting the VPN interface IP
address and the segment width.
This simple supplementary explanation could spare a lot of potential
users hours of ranting=E2=80=A6 ;)
Disclaimer: I don't do very much networking apart the usual into
Linux, so not on the head (nor the balls!)
Jean-Yves
next reply other threads:[~2017-05-02 14:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-02 14:51 Bzzzz [this message]
2017-05-02 14:57 ` Jonathon Fernyhough
2017-05-02 15:02 ` Ben Lebherz
2017-05-02 15:07 ` Bzzzz
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=20170502165145.2bf33eef@msi.defcon1 \
--to=lazyvirus@gmx.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).