From: John Sager <john@sager.me.uk>
To: wireguard@lists.zx2c4.com
Subject: Re: dns wireguard
Date: Sat, 5 Dec 2020 14:18:25 +0000 [thread overview]
Message-ID: <c3284f06-d3f7-904d-a0d3-74fff8e752bb@sager.me.uk> (raw)
In-Reply-To: <010801762ce31fbb-84ff5ca8-2674-451c-a4c7-b328af3e3a3f-000000@ap-southeast-2.amazonses.com>
Look at the routing table on A, B and the host with two tunnel connections
as well.
On 04/12/2020 08:34, Shulhan wrote:
>
>
>> On 3 Dec 2020, at 23.25, Esteban <esteban@gnumeria.fr> wrote:
>>
>> 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.
>>
>
> I think we need to see your configs, especially the AllowedIPs options, both on A and B (client and server).
>
>
prev parent reply other threads:[~2020-12-05 14:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-03 16:25 Esteban
2020-12-04 8:34 ` Shulhan
2020-12-05 14:18 ` John Sager [this message]
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=c3284f06-d3f7-904d-a0d3-74fff8e752bb@sager.me.uk \
--to=john@sager.me.uk \
--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).