On Tue, Aug 17, 2021 at 11:11 PM Waishon wrote:
>
> Hey there,
>
> I'm currently trying to setup a wireguard-tunnel inside a
> network-namespace as descriped in the documentation, which fails when
> using a domain as endpoint:
> https://www.wireguard.com/netns/
>
> First I've created the wireguard
Yes I did,
as described this isn't the problem. How should WireGuard resolve the
domain using the DNS server set inside the container, when it doesn't
have an internet connection?
Kind regards
Am Sa., 21. Aug. 2021 um 22:05 Uhr schrieb Marios Makassikis
:
>
> On Tue, Aug 17, 2021 at 11:11 PM Wa
Hey there,
thanks for your reply:
The reason why it works when using an IP instead of a domain is the
"birth namespace" concept of wiregurard. You're creating the WireGuard
interface inside your init-namespace (birth-namespace) which does have
an internet connection. The UDP socket for sending an
Hi,
Thanks for the kid and detailed answer, this is quite fascinating, I never
looked deep into wireguard and namespaces, only dealt with a couple of simple
IPsec + namespaces scenario before.
To me your issue seems to be valid, I hope you will get an answer from Jason
sooner or later.
Cheers
I am sorry, but I need to ask: if your namespace does not have an internet
connection how would you connect to your remote endpoint after the DNS lookup
issue is solved and you received the IP behind vpn.example.com?
Kind regards,
Domi
> 17.08.2021 dátummal, 23:06 időpontban Waishon írta:
>
>
Hey there,
I'm currently trying to setup a wireguard-tunnel inside a
network-namespace as descriped in the documentation, which fails when
using a domain as endpoint:
https://www.wireguard.com/netns/
First I've created the wireguard interface inside the birth-namespace
of the host using "ip link
