wireguard.lists.zx2c4.com archive mirror
 help / color / mirror / Atom feed
From: <danny.korpan@mailbox.org>
To: "'Ryan Whelan'" <rcwhelan@gmail.com>
Cc: wireguard@lists.zx2c4.com
Subject: AW: Routing only to latest peer in the config list seems to work
Date: Sat, 8 Sep 2018 10:36:47 +0200	[thread overview]
Message-ID: <018301d4474f$1565ab40$403101c0$@mailbox.org> (raw)
In-Reply-To: <CAM3m09TsnpW1VuZxEHDoCc2x-cbrS05unYCyCvNq=bP9LSNv2Q@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2537 bytes --]

Hi,

 

I’ve changed the AllowedIPs so that everyone has it’s 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 <mailto: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 <http://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 <http://192.168.50.0/24> 

[Peer]
#User 2
PublicKey = XXX
PresharedKey = XXX
#AllowedIPs = 192.168.50.0/24 <http://192.168.50.0/24> 

[Peer]
#User 3
PublicKey = XXX
PresharedKey = XXX
AllowedIPs = 192.168.50.0/24 <http://192.168.50.0/24> 

[Peer]
#User 4
PublicKey = XXX
PresharedKey = XXX
AllowedIPs = 192.168.50.0/24 <http://192.168.50.0/24> 



client.config
[Interface]
PrivateKey = XXX
DNS = 192.168.178.1
Address = 192.168.50.2/24 <http://192.168.50.2/24> 

[Peer]
PublicKey = XXX
PresharedKey = XXX
AllowedIPs = 192.168.50.0/24 <http://192.168.50.0/24> , 190.168.178.0/24 <http://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 <mailto:WireGuard@lists.zx2c4.com> 
https://lists.zx2c4.com/mailman/listinfo/wireguard


[-- Attachment #2: Type: text/html, Size: 6414 bytes --]

  reply	other threads:[~2018-09-08  8:36 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-29  7:43 Routing only to latest peer in the config list seems to work danny.korpan
2018-09-06 17:13 ` Ryan Whelan
2018-09-08  8:36   ` danny.korpan [this message]
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='018301d4474f$1565ab40$403101c0$@mailbox.org' \
    --to=danny.korpan@mailbox.org \
    --cc=rcwhelan@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).