From: Lonnie Abelbeck <lists@lonnie.abelbeck.com>
To: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: [PATCH 1/1] wg(8): rephrase wording on AllowedIPs
Date: Sun, 18 Feb 2018 10:10:35 -0600 [thread overview]
Message-ID: <11619261-079F-4ABC-869D-FF23E3C4DB35@lonnie.abelbeck.com> (raw)
In-Reply-To: <dead030cd0d96f25e6229931c9199b13a90578c4.1518955260.git.daniel@lublin.se>
On Feb 18, 2018, at 6:02 AM, Daniel Lublin <daniel@lublin.se> wrote:
> +AllowedIPs \(em a comma-separated list of IP (v4 or v6) addresses =
with CIDR
> +masks, declaring the sources of incoming traffic that are allowed =
through the
> +peer, and as well defining which destinations of outgoing traffic =
that will be
> +directed through the peer. The catch-all \fI0.0.0.0/0\fP may be =
specified for
> +matching all IPv4 addresses, and \fI::/0\fP may be specified for =
matching all
> +IPv6 addresses. May be specified multiple times. Required.
Personally, in an effort to make this more clear, from this reference:
Cryptokey Routing
https://www.wireguard.com/#cryptokey-routing
This quote offered clarity to me ...
--
When sending packets, the list of allowed IPs behaves as a sort of =
routing table, and when receiving packets, the list of allowed IPs =
behaves as a sort of access control list.
--
Lonnie
prev parent reply other threads:[~2018-02-18 16:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-18 12:02 [PATCH 0/1] Trying to rephrase man-file AllowedIPs again Daniel Lublin
2018-02-18 12:02 ` [PATCH 1/1] wg(8): rephrase wording on AllowedIPs Daniel Lublin
2018-02-18 16:10 ` Lonnie Abelbeck [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=11619261-079F-4ABC-869D-FF23E3C4DB35@lonnie.abelbeck.com \
--to=lists@lonnie.abelbeck.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).