From: Bzzzz <lazyvirus@gmx.com>
To: wireguard@lists.zx2c4.com
Subject: Re: Doc enhancement
Date: Tue, 2 May 2017 17:07:59 +0200 [thread overview]
Message-ID: <20170502170759.63a4b750@msi.defcon1> (raw)
In-Reply-To: <21b8fecd-119c-be0f-0f21-a4f03e2cb4a4@york.ac.uk>
On Tue, 2 May 2017 15:57:49 +0100
Jonathon Fernyhough <jonathon.fernyhough@york.ac.uk> wrote:
No, I mean e.g.: 10.11.12.1/24
at first, I thought it was a typo and added 2 'Address' lines in the
configuration file, one for the wg0 IP and one for the segment; but I
was wrong as the above notation is the way to go.
However, it is not publicized anywhere, so it took me 'some' time to
figure this out.
> Do you mean 192.168.88.0/24 ? That's the standard annotation for IP
> subnets (e.g. 10.0.0.0/16, 192.168.0.0/24, 8.8.8.8/32).
prev parent reply other threads:[~2017-05-02 14:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-02 14:51 Bzzzz
2017-05-02 14:57 ` Jonathon Fernyhough
2017-05-02 15:02 ` Ben Lebherz
2017-05-02 15:07 ` Bzzzz [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=20170502170759.63a4b750@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).