From: Lars Francke <lars.francke@gmail.com>
To: phil@sunfi.sh
Cc: wireguard@lists.zx2c4.com
Subject: Re: Question about AllowedIPs and proper "mesh" setup
Date: Tue, 6 Nov 2018 21:41:53 +0100 [thread overview]
Message-ID: <CAD-Ua_gLEPjZ9ufHnLtPM-eqAj+t1pN0uFbOpx3zobF5oHSPDw@mail.gmail.com> (raw)
In-Reply-To: <3jyAZC1J0MGdvAW-Ldzv1OiVrcdJ-GLbqgVTNY2U_1Qp-SstlhEUK9l82mBR9FwfS3F4yiwnNREeFzMaSlR0L6cw2M58JhcB3itJYNBTOUg=@sunfi.sh>
[-- Attachment #1.1: Type: text/plain, Size: 1448 bytes --]
Phil, Matthias,
thanks for the answers. I haven't received Matthias answer but I can see it
in the archive.
The reason I wanted to do it the way I initially described is laziness. I'm
setting up the machines using Ansible[0]. It'd be great if I didn't need
any special cases but it seems that that's going to be way easier than
figuring out another way (which doesn't even seem to exist yet) ;-)
Thank you both!
Cheers,
Lars
[0] <https://github.com/opencore/ansible_wireguard> (It's not beautiful but
it does what I need)
On Tue, Nov 6, 2018 at 9:16 PM Phil Hofer <phil@sunfi.sh> wrote:
> > Now I want to add an outside client into the mix (e.g. my laptop). I
> want to be able to connect to just one of those hosts and have that host
> forward my packages to the others.
> > I can get it to work if I pick _one_ specific jump host but I haven't
> managed to set it up in a way that I can connect to any of them.
>
> You might consider setting up just one of your servers
> as a gateway for a subnet dedicated to your client machine(s).
> Then add routes on your servers to the gateway.
>
> For example, set up 10.0.0.1 as the gateway to 10.0.1.0/24,
> and set your client machine up as 10.0.1.1. Machines on
> 10.0.0.0/24 remain connected directly.
>
> If you need to be able to route through any one of
> your servers on an ad-hoc basis, then you'll need some
> additional routing protocol magic, as Matthias suggested.
>
> Cheers,
> Phil
[-- Attachment #1.2: Type: text/html, Size: 2082 bytes --]
[-- Attachment #2: Type: text/plain, Size: 148 bytes --]
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard
next prev parent reply other threads:[~2018-11-06 20:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-06 8:01 Question about AllowedIPs and proper "mesh" setup Lars Francke
2018-11-06 20:04 ` Matthias Urlichs
2018-11-06 20:16 ` Phil Hofer
2018-11-06 20:41 ` Lars Francke [this message]
2018-11-08 19:33 ` Brian
2018-11-07 1:55 ` KeXianbin(http://diyism.com)
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=CAD-Ua_gLEPjZ9ufHnLtPM-eqAj+t1pN0uFbOpx3zobF5oHSPDw@mail.gmail.com \
--to=lars.francke@gmail.com \
--cc=phil@sunfi.sh \
--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).