dns wireguard

[John Sager]

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 at 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).
> 
>