WireGuard Archive on lore.kernel.org
 help / color / Atom feed
From: Gunnar Niels <gunnar.s.niels@gmail.com>
To: M Rubon <rubonmtz@gmail.com>, Rich Brown <richb.hanover@gmail.com>
Cc: "Tomcsanyi, Domonkos" <domi@tomcsanyi.net>, wireguard@lists.zx2c4.com
Subject: Re: Confused about AllowedIPs meaning?
Date: Wed, 29 Jul 2020 12:27:57 -0400
Message-ID: <e5953067-a158-0a64-b6a0-1602d8fd22d0@gmail.com> (raw)
In-Reply-To: <CAJ24mqCQ+jyzZ13ji+z31-=Rj1rfBrLDtq1bZMAMO+rgsxKXCg@mail.gmail.com>

On 7/29/20 12:11 PM, M Rubon wrote:
> AllowedIPs  — a comma-separated list of IP (v4 or v6) addresses
> with CIDR masks which are allowed as
>         destination addresses when sending via this peer and are
> allowed as source addresses when receiving via this peer.

+1, the man page definition you cited is somewhat ambiguous; this is a more
explicit definition that clears up the ambiguity.

I really appreciate all the responses, it's been very helpful. I've waiting on
the hardware I've selected to ship before deploying the suggestions. I'm planning
on using a pfsense default gateway for both networks and running RPi 4s
with static addresses on both subnets as wireguard gateways between the two nets
(they have gigabit NICs which is a nice upgrade over my older 3s, especially
for this use-case). From some of the PFSense community discussions, it doesn't
look like they're ready to accept an official wireguard plugin, although there
are some community contributions.

I will report back after I've my hardware has arrived and I've had some time to


  reply index

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-26 10:57 Gunnar Niels
2020-07-28 16:30 ` Lonnie Abelbeck
2020-07-28 21:12 ` Tomcsanyi, Domonkos
2020-07-28 21:33   ` Rich Brown
2020-07-29 16:11     ` M Rubon
2020-07-29 16:27       ` Gunnar Niels [this message]
2020-07-29 22:18     ` Ivan Labáth
2020-07-30  0:57       ` Rich Brown
2020-07-30 14:02         ` M Rubon
2020-07-30 18:08           ` Ivan Labáth
2020-07-30 21:03             ` Rich Brown
2020-07-29 10:40 ` John Sager

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=e5953067-a158-0a64-b6a0-1602d8fd22d0@gmail.com \
    --to=gunnar.s.niels@gmail.com \
    --cc=domi@tomcsanyi.net \
    --cc=richb.hanover@gmail.com \
    --cc=rubonmtz@gmail.com \
    --cc=wireguard@lists.zx2c4.com \


* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

WireGuard Archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/wireguard/0 wireguard/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 wireguard wireguard/ https://lore.kernel.org/wireguard \
	public-inbox-index wireguard

Example config snippet for mirrors

Newsgroup available over NNTP:

AGPL code for this site: git clone https://public-inbox.org/public-inbox.git