From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: danny.korpan@mailbox.org Received: from krantz.zx2c4.com (localhost [127.0.0.1]) by krantz.zx2c4.com (ZX2C4 Mail Server) with ESMTP id 44fadfae for ; Sat, 8 Sep 2018 08:36:24 +0000 (UTC) Received: from mx2.mailbox.org (mx2.mailbox.org [80.241.60.215]) by krantz.zx2c4.com (ZX2C4 Mail Server) with ESMTP id 5941225f for ; Sat, 8 Sep 2018 08:36:23 +0000 (UTC) From: To: "'Ryan Whelan'" References: <006501d43f6b$eb516e60$c1f44b20$@mailbox.org> In-Reply-To: Subject: AW: Routing only to latest peer in the config list seems to work Date: Sat, 8 Sep 2018 10:36:47 +0200 Message-ID: <018301d4474f$1565ab40$403101c0$@mailbox.org> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0184_01D4475F.D8EE7B40" Cc: wireguard@lists.zx2c4.com Reply-To: danny.korpan@mailbox.org List-Id: Development discussion of WireGuard List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , This is a multipart message in MIME format. ------=_NextPart_000_0184_01D4475F.D8EE7B40 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hi, =20 I=E2=80=99ve changed the AllowedIPs so that everyone has it=E2=80=99s = own dedicated IP. Still the same problem. No routing. =20 Kind Regards, Danny =20 Von: Ryan Whelan =20 Gesendet: Donnerstag, 6. September 2018 19:14 An: danny.korpan@mailbox.org Cc: WireGuard mailing list Betreff: Re: Routing only to latest peer in the config list seems to = work =20 You're using the same AllowedIPs for multiple peers. =20 On Thu, Sep 6, 2018 at 12:15 PM > 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 =3D 192.168.50.1/24 =20 PostUp =3D iptables -A FORWARD -i wg0 -j ACCEPT; iptables -t nat -A POSTROUTING -o eth0 -j MASQUERADE PostDown =3D iptables -D FORWARD -i wg0 -j ACCEPT; iptables -t nat -D POSTROUTING -o eth0 -j MASQUERADE ListenPort =3D 51820 PrivateKey =3D XXX [Peer] #User 1 PublicKey =3D XXX PresharedKey =3D XXX AllowedIPs =3D 192.168.50.0/24 =20 [Peer] #User 2 PublicKey =3D XXX PresharedKey =3D XXX #AllowedIPs =3D 192.168.50.0/24 =20 [Peer] #User 3 PublicKey =3D XXX PresharedKey =3D XXX AllowedIPs =3D 192.168.50.0/24 =20 [Peer] #User 4 PublicKey =3D XXX PresharedKey =3D XXX AllowedIPs =3D 192.168.50.0/24 =20 client.config [Interface] PrivateKey =3D XXX DNS =3D 192.168.178.1 Address =3D 192.168.50.2/24 =20 [Peer] PublicKey =3D XXX PresharedKey =3D XXX AllowedIPs =3D 192.168.50.0/24 , = 190.168.178.0/24 =20 Endpoint =3D my.remote.server:51820 PersistentKeepalive =3D 25 My sysctl.conf includes net.ipv4.conf.all.proxy_arp =3D 1 net.ipv4.ip_forward =3D 1 Does anybody have an idea? Kind Regards, Danny _______________________________________________ WireGuard mailing list WireGuard@lists.zx2c4.com =20 https://lists.zx2c4.com/mailman/listinfo/wireguard ------=_NextPart_000_0184_01D4475F.D8EE7B40 Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: quoted-printable

Hi,

 

I=E2=80=99ve changed the AllowedIPs so that everyone has = it=E2=80=99s own dedicated IP. Still the same problem. No = routing.

 

Kind Regards,

Danny

 

Von: Ryan = Whelan <rcwhelan@gmail.com>
Gesendet: Donnerstag, 6. = September 2018 19:14
An: = danny.korpan@mailbox.org
Cc: WireGuard mailing list = <wireguard@lists.zx2c4.com>
Betreff: Re: Routing only to = latest peer in the config list seems to = work

 

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 =3D 192.168.50.1/24
PostUp =3D iptables -A FORWARD = -i wg0 -j ACCEPT; iptables -t nat -A
POSTROUTING -o eth0 -j = MASQUERADE
PostDown =3D iptables -D FORWARD -i wg0 -j ACCEPT; = iptables -t nat -D
POSTROUTING -o eth0 -j MASQUERADE
ListenPort = =3D 51820
PrivateKey =3D XXX

[Peer]
#User 1
PublicKey = =3D XXX
PresharedKey =3D XXX
AllowedIPs =3D 192.168.50.0/24

[Peer]
#User = 2
PublicKey =3D XXX
PresharedKey =3D XXX
#AllowedIPs =3D 192.168.50.0/24

[Peer]
#User = 3
PublicKey =3D XXX
PresharedKey =3D XXX
AllowedIPs =3D 192.168.50.0/24

[Peer]
#User = 4
PublicKey =3D XXX
PresharedKey =3D XXX
AllowedIPs =3D 192.168.50.0/24



client.config
[In= terface]
PrivateKey =3D XXX
DNS =3D 192.168.178.1
Address =3D = 192.168.50.2/24

[Peer]
PublicKey =3D = XXX
PresharedKey =3D XXX
AllowedIPs =3D 192.168.50.0/24, = 190.168.178.0/24
Endpoint =3D = my.remote.server:51820
PersistentKeepalive =3D 25

My = sysctl.conf includes
net.ipv4.conf.all.proxy_arp =3D = 1
net.ipv4.ip_forward =3D 1

Does anybody have an = idea?


Kind = Regards,
Danny

_______________________________________________<= br>WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard<= o:p>

------=_NextPart_000_0184_01D4475F.D8EE7B40--