From: Grant Haywood <mrgranthaywood@gmail.com>
To: wireguard@lists.zx2c4.com
Subject: only last configured peer has allowed-ips
Date: Mon, 13 Nov 2017 02:38:26 +0000 [thread overview]
Message-ID: <CAPayrd584iu0B=0ojTPdkZNQzwfCfE3SUcqst3NAHjw6efWqJQ@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1644 bytes --]
When I run the following on a wireguard instance
wireguard@lists.zx2c4.com
wg set wg0 peer *SOMEPUB1* allowed-ips 0.0.0.0/0 persistent-keepalive 25
wg set wg0 peer *SOMEPUB2* allowed-ips 0.0.0.0/0 persistent-keepalive 25
only the last key gets set with an allowed-ips directive
interface: wg0
public key: *HOSTKEY*
private key: (hidden)
listening port: 51820
peer: *SOMEPUB2*
endpoint: *SOMEIP*:38568
allowed ips: 0.0.0.0/0
latest handshake: 1 minute, 11 seconds ago
transfer: 4.81 KiB received, 3.47 KiB sent
persistent keepalive: every 25 seconds
peer: *SOMEPUB1*
endpoint: *SOMEIP*:36411
allowed ips: (none) #<< This appears wrong
latest handshake: 1 minute, 24 seconds ago
transfer: 44.05 KiB received, 47.68 KiB sent
persistent keepalive: every 25 seconds
I cannot pass traffic from SOMEPUB1, and no handshake occurs
if SOMEPUB1 occurs last in the sequence of running wg set commands, it
retains the allowed-ips configuration and it CAN pass traffic, so it seems
only the last command run for me is valid for allowed-ips
the host is running the following
ii wireguard-dkms 0.0.20171111-wg1~zesty
all fast, modern, secure kernel VPN tunnel (DKMS version)
ii wireguard-tools 0.0.20171111-wg1~zesty
amd64 fast, modern, secure kernel VPN tunnel (userland utilities)
one of the peers is running the same, the other is a rasberry pi built from
source snapshot as described on wireguard.com (WireGuard-0.0.20171111)
Am I missing something or is there an issue with configuring 2 peers with
0.0.0.0/0 in this release?
Thanks in advance
[-- Attachment #2: Type: text/html, Size: 2696 bytes --]
next reply other threads:[~2017-11-13 2:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-13 2:38 Grant Haywood [this message]
2017-11-13 9:12 ` Aaron Jones
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='CAPayrd584iu0B=0ojTPdkZNQzwfCfE3SUcqst3NAHjw6efWqJQ@mail.gmail.com' \
--to=mrgranthaywood@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 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).