From: Andreas Fink <finkandreas@web.de>
To: wireguard@lists.zx2c4.com
Subject: Connection between two clients
Date: Wed, 15 Aug 2018 09:17:00 +0200 [thread overview]
Message-ID: <20180815091700.0d1d5923@web.de> (raw)
Hello,
I have a problem establishing a direct connection between two clients,
my setup is the following:
Client1 <--> Server <--> Client2
i.e. I have a publicly reachable server, and two clients that are
connected to the server. My configurations are:
Server.conf
[Interface]
PrivateKey = ServerPrivateKey
ListenPort = 51820
Address = 192.168.12.1/24
[Peer]
PublicKey = Client1PublicKey
AllowedIPs = 192.168.12.3/32
[Peer]
PublicKey = Client1PublicKey
AllowedIPs = 192.168.12.2/32
Client1.conf
[Interface]
PrivateKey = Client1PrivateKey
ListenPort = 21003
Address = 192.168.12.3/24
[Peer]
PublicKey = ServerPublicKey
Endpoint = myserver.com:51820
AllowedIPs = 192.168.12.1/24
PersistentKeepalive = 25
Client2.conf
[Interface]
PrivateKey = Client2PrivateKey
ListenPort = 21002
Address = 192.168.12.2/24
[Peer]
PublicKey = ServerPublicKey
Endpoint = myserver.com:51820
AllowedIPs = 192.168.12.1/24
PersistentKeepalive = 25
I am able to ping between client1 to server and client2 to server.
However trying to ping client2 from client1 directly fails...
Looking at the server with tcpdump I can see, that there is an incoming
ping from 192.168.12.3 > 192.168.12.2, however there is nothing
reaching at 192.168.12.2. The ping is not forwarded to 192.168.12.2.
Do I need to setup iptables rules? What's the easiest way to get a
direct connection between two clients?
Cheers
Andreas
next reply other threads:[~2018-08-15 7:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-15 7:17 Andreas Fink [this message]
2018-08-16 19:40 ` Connection between two clients Kalin KOZHUHAROV
2018-08-16 19:52 ` Eldon
2018-08-17 6:00 ` Andreas Fink
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=20180815091700.0d1d5923@web.de \
--to=finkandreas@web.de \
--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.