From: <wireguard@lindenberg.one>
To: "'WireGuard mailing list'" <wireguard@lists.zx2c4.com>
Subject: two client connections -> crash?
Date: Mon, 13 Jul 2020 20:53:35 +0200 [thread overview]
Message-ID: <08a201d65946$e9c84f90$bd58eeb0$@lindenberg.one> (raw)
I am trying to configure one client system (Ubuntu 18.04.4 LTS (GNU/Linux 5.3.0-62-generic x86_64)) against two servers. The configuration is very similar:
root@Mailcow:/home/joachim# cat /etc/wireguard/wg0-client.conf
[Interface]
Address = 10.200.200.2/24
PrivateKey = ***
DNS = 8.8.8.8 #10.200.200.1
[Peer]
PublicKey = qn6CTz578gbrYpzYkvV2okoqkIFHKye+mRj4i/I8Sz8=
Endpoint = fire.lindenberg.one:51820
AllowedIPs = 0.0.0.0/0
PersistentKeepalive = 21
root@Mailcow:/home/joachim# cat /etc/wireguard/wg1-client.conf
[Interface]
Address = 10.200.201.2/24
PrivateKey = ***
DNS = 8.8.8.8 #10.200.200.1
[Peer]
PublicKey = QAJANxtuAvdT+HR3fP1I2DXq0Azl0T3jF5s+cW7foSA=
Endpoint = nc.lindenberg.one:51820
AllowedIPs = 0.0.0.0/0
PersistentKeepalive = 21
Wg-quick up wg0-client ist at system startup. Now unfortunately when I do wg-quick up wg1-client the network stack kind of crashes. The command does not terminate, and connectivity on all interfaces is broken.
Is this a configuration issue? Should I change ports to be different? Is there some other issue?
Do I have to define two interfaces or could I have just one with multiple peers? But how could I then specify which tunnel to use?
Any suggestion welcome..
Thanks, Joachim
next reply other threads:[~2020-07-13 18:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-13 18:53 wireguard [this message]
2020-07-13 23:51 ` two client connections -> crash? Jason A. Donenfeld
2020-07-14 10:11 ` M. Dietrich
2020-07-14 13:43 ` AW: " Joachim Lindenberg
2020-07-14 13:50 ` Xand Meaden
2020-07-20 14:23 ` AW: " wireguard
2020-07-14 17:54 ` M. Dietrich
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='08a201d65946$e9c84f90$bd58eeb0$@lindenberg.one' \
--to=wireguard@lindenberg.one \
--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.