From: Matthias Urlichs <matthias@urlichs.de>
To: wireguard@lists.zx2c4.com
Subject: Re: wg addconf :: AllowedIPs gets deleted with the additions of peers
Date: Tue, 26 Jun 2018 10:13:27 +0200 [thread overview]
Message-ID: <d1f72e76-7477-5aa6-88c6-2908c4be68f5@urlichs.de> (raw)
In-Reply-To: <b4b972dc-7852-4b43-0015-2963437e1de3@gmail.com>
On 26.06.2018 09:34, Adrian Sevcenco wrote:
> Then, how can i set a default allow everything for each peer? Should i
> make a different tunnel for each peer?
Why would you want to? You need IP routing information for each peer,
just like you need their public key. You can't have two peers / networks
/ whatever with the same IP address or address range. That's always been
the case, wireguard or no wireguard.
--
-- Matthias Urlichs
next prev parent reply other threads:[~2018-06-26 8:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-25 19:51 Adrian Sevcenco
2018-06-25 19:55 ` Toke Høiland-Jørgensen
2018-06-25 20:00 ` Adrian Sevcenco
2018-06-25 20:37 ` Toke Høiland-Jørgensen
2018-06-26 7:34 ` Adrian Sevcenco
2018-06-26 7:44 ` Eric Light
2018-06-26 8:13 ` Matthias Urlichs [this message]
2018-06-26 10:56 ` Toke Høiland-Jørgensen
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=d1f72e76-7477-5aa6-88c6-2908c4be68f5@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).