From: Adrian Sevcenco <adrian.sev@gmail.com>
To: "Toke Høiland-Jørgensen" <toke@toke.dk>,
"WireGuard mailing list" <wireguard@lists.zx2c4.com>
Subject: Re: wg addconf :: AllowedIPs gets deleted with the additions of peers
Date: Tue, 26 Jun 2018 10:34:48 +0300 [thread overview]
Message-ID: <b4b972dc-7852-4b43-0015-2963437e1de3@gmail.com> (raw)
In-Reply-To: <87woummwlh.fsf@toke.dk>
On 06/25/2018 11:37 PM, Toke H=C3=B8iland-J=C3=B8rgensen wrote:
> Adrian Sevcenco <adrian.sev@gmail.com> writes:
>=20
>> On 06/25/2018 10:55 PM, Toke H=C3=B8iland-J=C3=B8rgensen wrote:
>>> Adrian Sevcenco <adrian.sev@gmail.com> writes:
>>>
>>>> Hi! It seems that AllowedIPs declaration gets erased when peers are
>>>> added with addconf
>>>
>>> You can't have the same AllowedIPs for two different peers... :)
>>
>> Err... so, it's a bug or a feature?
>=20
> A feature. The AllowedIPs controls which IP addresses will be routed to=
> that peer. They refer to addresses inside the tunnel. So depending on
> your setup you'd specify the single IP you assign each peer, or possibl=
y
> any subnets behind that peer you want routed through the tunnel.
Then, how can i set a default allow everything for each peer? Should i=20
make a different tunnel for each peer?
But given your explanation i still feel that it is a bug that when an=20
AllowIPs is declared with the addition of a second peer the declaration=20
from the first peer gets erased ...
It should be either a global setting per tunnel OR an individual setting =
per peer (in which case it should stay set)
Thank you!!
Adrian
>=20
>> If it is a feature how can i make server accept whatever ip get the
>> client(s) in various networks?
>=20
> Changing IPs *on the outside* of the tunnel will be accepted
> automatically. The Endpoint specifier is only the initial address; if a=
> device changes its IP, it'll just keep sending packets from the new IP,=
> and because they are authenticated by the crypto, the other peer will
> accept them and change its notion of what IP the other peer is
> reachable at automatically. So as long as only one peer changes its IP
> at a time, roaming mostly just works :)
>=20
> -Toke
>=20
next prev parent reply other threads:[~2018-06-26 7:29 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 [this message]
2018-06-26 7:44 ` Eric Light
2018-06-26 8:13 ` Matthias Urlichs
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=b4b972dc-7852-4b43-0015-2963437e1de3@gmail.com \
--to=adrian.sev@gmail.com \
--cc=toke@toke.dk \
--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).