From: Ryan Whelan <rcwhelan@gmail.com>
To: danny.korpan@mailbox.org
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: Routing only to latest peer in the config list seems to work
Date: Thu, 6 Sep 2018 13:13:35 -0400 [thread overview]
Message-ID: <CAM3m09TsnpW1VuZxEHDoCc2x-cbrS05unYCyCvNq=bP9LSNv2Q@mail.gmail.com> (raw)
In-Reply-To: <006501d43f6b$eb516e60$c1f44b20$@mailbox.org>
[-- Attachment #1: Type: text/plain, Size: 1891 bytes --]
You're using the same AllowedIPs for multiple peers.
On Thu, Sep 6, 2018 at 12:15 PM <danny.korpan@mailbox.org> wrote:
> Hi,
>
> I have the problem with my wireguard server, that only the latest user
> "peer" from the server config can route/ping to the internal wireguard
> server IP or the clients in the network behind the wireguard server upon
> successful connection. All peers can connect to the server, but only the
> latest in the list last can ping other servers.
> I can't locate the error in the configs... does anybody have an idea?
>
> My wireguard server and client version is using 0.0.20180809-wg1~xenial
> with
> Ubuntu 18.04.1
>
> wg0.conf
> [Interface]
> Address = 192.168.50.1/24
> PostUp = iptables -A FORWARD -i wg0 -j ACCEPT; iptables -t nat -A
> POSTROUTING -o eth0 -j MASQUERADE
> PostDown = iptables -D FORWARD -i wg0 -j ACCEPT; iptables -t nat -D
> POSTROUTING -o eth0 -j MASQUERADE
> ListenPort = 51820
> PrivateKey = XXX
>
> [Peer]
> #User 1
> PublicKey = XXX
> PresharedKey = XXX
> AllowedIPs = 192.168.50.0/24
>
> [Peer]
> #User 2
> PublicKey = XXX
> PresharedKey = XXX
> #AllowedIPs = 192.168.50.0/24
>
> [Peer]
> #User 3
> PublicKey = XXX
> PresharedKey = XXX
> AllowedIPs = 192.168.50.0/24
>
> [Peer]
> #User 4
> PublicKey = XXX
> PresharedKey = XXX
> AllowedIPs = 192.168.50.0/24
>
>
>
> client.config
> [Interface]
> PrivateKey = XXX
> DNS = 192.168.178.1
> Address = 192.168.50.2/24
>
> [Peer]
> PublicKey = XXX
> PresharedKey = XXX
> AllowedIPs = 192.168.50.0/24, 190.168.178.0/24
> Endpoint = my.remote.server:51820
> PersistentKeepalive = 25
>
> My sysctl.conf includes
> net.ipv4.conf.all.proxy_arp = 1
> net.ipv4.ip_forward = 1
>
> Does anybody have an idea?
>
>
> Kind Regards,
> Danny
>
> _______________________________________________
> WireGuard mailing list
> WireGuard@lists.zx2c4.com
> https://lists.zx2c4.com/mailman/listinfo/wireguard
>
[-- Attachment #2: Type: text/html, Size: 3114 bytes --]
next prev parent reply other threads:[~2018-09-06 17:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-29 7:43 danny.korpan
2018-09-06 17:13 ` Ryan Whelan [this message]
2018-09-08 8:36 ` AW: " danny.korpan
2018-09-08 10:21 ` Steven Honson
2018-09-08 17:28 ` AW: " danny.korpan
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='CAM3m09TsnpW1VuZxEHDoCc2x-cbrS05unYCyCvNq=bP9LSNv2Q@mail.gmail.com' \
--to=rcwhelan@gmail.com \
--cc=danny.korpan@mailbox.org \
--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).