All of lore.kernel.org
 help / color / mirror / Atom feed
From: Adrian Sevcenco <adrian.sev@gmail.com>
To: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: wg addconf :: AllowedIPs gets deleted with the additions of peers
Date: Mon, 25 Jun 2018 22:51:51 +0300	[thread overview]
Message-ID: <a989a217-9e18-5e5f-2a97-fa3ac81ccb87@gmail.com> (raw)

Hi! It seems that AllowedIPs declaration gets erased when peers are 
added with addconf
So, we have the interface :
wg showconf wg0
[Interface]
ListenPort = 43333
PrivateKey = <XXX>

and we add a peer
wg addconf wg0 hal.conf.p1
[Monday 25.06.18 22:48] root@sev : /etc/wireguard/peers_server $
wg showconf wg0
[Interface]
ListenPort = 43333
PrivateKey = KLLZ9i4ffUeCv+e6cs7V7+jKM3KJtgaRkEbt52UCcEU=

[Peer]
PublicKey = /azluhJf0RYaIxu6rHRHx6+fKfivwOnKVp9Naefgsk0=
AllowedIPs = 0.0.0.0/0

then we add a second peer :
wg addconf wg0 x360.conf.p2
[Monday 25.06.18 22:49] root@sev : /etc/wireguard/peers_server $
wg showconf wg0
[Interface]
ListenPort = 43333
PrivateKey = KLLZ9i4ffUeCv+e6cs7V7+jKM3KJtgaRkEbt52UCcEU=

[Peer]
PublicKey = /azluhJf0RYaIxu6rHRHx6+fKfivwOnKVp9Naefgsk0=
Endpoint = 79.115.160.101:43333

[Peer]
PublicKey = 0bC+LP/8fsjjn9RSdq+Bz1qdgPRV3CYE/4fEiOqjrC4=
AllowedIPs = 0.0.0.0/0

the AllowedIPs declaration was erased from first peer..

the file contents :
[Monday 25.06.18 22:49] root@sev : /etc/wireguard/peers_server $
cat hal.conf.p1
[Peer]
PublicKey = /azluhJf0RYaIxu6rHRHx6+fKfivwOnKVp9Naefgsk0=
AllowedIPs = 0.0.0.0/0

[Monday 25.06.18 22:50] root@sev : /etc/wireguard/peers_server $
cat x360.conf.p2
[Peer]
PublicKey = 0bC+LP/8fsjjn9RSdq+Bz1qdgPRV3CYE/4fEiOqjrC4=
AllowedIPs = 0.0.0.0/0

Thank you!
Adrian

             reply	other threads:[~2018-06-25 19:46 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-25 19:51 Adrian Sevcenco [this message]
2018-06-25 19:55 ` wg addconf :: AllowedIPs gets deleted with the additions of peers 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
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=a989a217-9e18-5e5f-2a97-fa3ac81ccb87@gmail.com \
    --to=adrian.sev@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.