From: Esteban <esteban@gnumeria.fr>
To: wireguard@lists.zx2c4.com
Subject: dns wireguard
Date: Thu, 3 Dec 2020 17:25:13 +0100 [thread overview]
Message-ID: <38259275-2f96-feb5-d3e8-70aafb862f41@gnumeria.fr> (raw)
Hello, I take the liberty to contact you, I have a huge bug, and it's
not me who is at fault, I prefer to specify it, some friends have
exactly the same bug as me.
I like wireguard because it's very easy to connect on several tunnels
simultaneously but when, (I'll schematize)
I have two wireguard customers
In the configuration of the wireguard A server I will have in DNS
172.16.150.1
And in the configuration of the wireguard server B I will have in DNS
172.16.155.1
I start by connecting to the first client, the wireguard A server.
I manage to ping the DNS of this server A.
I keep the connection from server A and connect to server B.
I can ping the DNS of server A but not the DNS of server B.
And if I reverse the connection priorities, so I start by connecting to
the client of the wireguard server B, I can ping the dns server of this
server B.
And I keep this connection and when I connect to the client of wireguard
server A, I can continue to ping the DNS of server B, but I cannot ping
the DNS of server A.
To conclude, simultaneous wireguard connections work at the ip level.
But when two wireguard configurations are up, I can ping the dns of the
first wireguard I connected but not the second.
When I talk about dns, it's the DNS =
In the wireguard customer files. Two wireguard up configuration with DNS
Only one DNS is taken into account, the first wireguard I connected to.
And the dns of the second wireguard I connect to does not ping.
(Problem on gnu/linux, I don't know about windows)
Best regards.
next reply other threads:[~2020-12-03 21:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-03 16:25 Esteban [this message]
2020-12-04 8:34 ` Shulhan
2020-12-05 14:18 ` John Sager
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=38259275-2f96-feb5-d3e8-70aafb862f41@gnumeria.fr \
--to=esteban@gnumeria.fr \
--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).