From: Reuben Martin <reuben.m.work@gmail.com>
To: Ryan Whelan <rcwhelan@gmail.com>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: Another allowed-ips question
Date: Sat, 18 Nov 2017 17:55:38 -0600 [thread overview]
Message-ID: <CALJ2VGa=4faoudZkttX8Whsm5mysq0GPe+vDjREYtb7+Syukzg@mail.gmail.com> (raw)
In-Reply-To: <CAM3m09QZc=kJoXUQvCpCVQG62TeDX0B4BdcuUU3A9T2Lfg10VQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1037 bytes --]
On Nov 18, 2017 5:44 PM, "Ryan Whelan" <rcwhelan@gmail.com> wrote:
I'm working on a system where Wireguard machines can connect directly to
one another as well as communicate with one another via an intermediary
router (or 'server').
When 2 machines directly connect to one another, the allowed-ips setting is
obviously a non-issue; what i'm struggling with is if they are unable to
communicate directly and build routes to one another via an intermediary
router (which is also connected to each 'client' via wireguard). Unless
the 'server' NATs the traffic, the allowed-ips setting will prevent the
'clients' from communicating. Am i missing something?
I'm trying to avoid building a wg interface for each peer connection if
possible, but i'm failing to see any other way around it. Either NAT at
the intermediary router or create an interface per-peer.
Are there other options?
I have something kinda similar. I set up vxlan connections overtop of the
wireguard connections and added the vxlan interfaces to bridges.
-Reuben
[-- Attachment #2: Type: text/html, Size: 1578 bytes --]
next prev parent reply other threads:[~2017-11-18 23:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-18 23:44 Ryan Whelan
2017-11-18 23:55 ` Reuben Martin [this message]
2017-11-22 23:51 ` Jason A. Donenfeld
2017-12-05 14:05 ` Ryan Whelan
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='CALJ2VGa=4faoudZkttX8Whsm5mysq0GPe+vDjREYtb7+Syukzg@mail.gmail.com' \
--to=reuben.m.work@gmail.com \
--cc=rcwhelan@gmail.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).