From: Matthias Urlichs <matthias@urlichs.de>
To: wireguard@lists.zx2c4.com
Subject: Re: Question about AllowedIPs and proper "mesh" setup
Date: Tue, 6 Nov 2018 21:04:57 +0100 [thread overview]
Message-ID: <c645fd95-ffc6-f46c-0911-49cf021f8162@urlichs.de> (raw)
In-Reply-To: <CAD-Ua_hRW4RyOMrP3jX3hAAVLJCLHXYPvYY_PaK0y-=r_HhTQQ@mail.gmail.com>
On 06.11.18 09:01, Lars Francke wrote:
> I haven't managed to set it up in a way that I can connect to any of them.
You can't, at least not out-of-the-box. How would these other hosts know
how to reach your client?
You need some sort of route propagation protocol (a couple of them
exist) and some way to monitor the wireguard interface state (no code
that I know of exists that does this) and feed that into the routing
protocol (ditto).
--
-- Matthias Urlichs
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard
next prev parent reply other threads:[~2018-11-06 20:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-06 8:01 Lars Francke
2018-11-06 20:04 ` Matthias Urlichs [this message]
2018-11-06 20:16 ` Phil Hofer
2018-11-06 20:41 ` Lars Francke
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=c645fd95-ffc6-f46c-0911-49cf021f8162@urlichs.de \
--to=matthias@urlichs.de \
--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).