From: Shulhan <ms@kilabit.info>
To: Devanath S <s.devanath@gmail.com>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: wireguard-go on MACos
Date: Tue, 20 Sep 2022 01:29:39 +0700 [thread overview]
Message-ID: <20220920012939.78a8be42@inspiro.localdomain> (raw)
In-Reply-To: <CADjMg7XtPWoozpBikNGP=EDCYvH=dr3Uo60emPXGvUv0MbJvVQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1245 bytes --]
Hi Dev,
On Mon, 19 Sep 2022 10:47:29 -0700
Devanath S <s.devanath@gmail.com> wrote:
> Hi All,
>
> We are using wireguard-go on MACOS/LINUX and a dns-proxy is listening
> on wireguard device. dns-proxy is receiving dns requests from the
> desktop (destined to wireguarddeviceip:53) on linuxos. But the same
> does not work on MACos.
>
> I have tried to create tun/ap using go-library (water) and was able to
> receive the requests, but the same fails when using a wireguard device
> created using wireguard-go. Also ping to wireguard device ip from the
> desktop fails miserably.
>
I assume you want to make all peers request to the same DNS server, yes?
In that case, instead of installing dns-proxy on each user, setup a
central DNS server and let the WireGuard handle the rest.
For example, in my experience, I setup rescached [1] (or any DNS
caches/forwarder) on the "server" peer at 10.8.0.1 and set the DNS
option on each "client" peer to that address
[Interface]
...
DNS = 10.8.0.1
With this mode, client does not need to install or setup anything except
the WireGuard application.
[1] https://kilabit.info/project/rescached
--
{ "git":"git.sr.ht/~shulhan", "site":"kilabit.info" }
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2022-09-19 18:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-19 17:47 Devanath S
2022-09-19 18:29 ` Shulhan [this message]
2022-09-19 18:55 ` Devanath S
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=20220920012939.78a8be42@inspiro.localdomain \
--to=ms@kilabit.info \
--cc=s.devanath@gmail.com \
--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).