From: Christophe-Marie Duquesne <chmd@chmd.fr>
To: vtol <vtol@gmx.net>, wireguard@lists.zx2c4.com
Subject: Re: WG endpoint node exit to inet and DNS resolver
Date: Mon, 7 May 2018 15:23:45 +0200 [thread overview]
Message-ID: <CAHLp1YmAf+hD+iHD+cZPorqMp-m=Aw_nJ5E2TcQYrXt-y7FZNQ@mail.gmail.com> (raw)
In-Reply-To: <586e6364-d143-2b9b-8ea0-940072a9db9a@gmx.net>
[-- Attachment #1: Type: text/plain, Size: 1486 bytes --]
Re-adding the ML that I removed from my response by mistake
On Mon, May 7, 2018 at 3:12 PM, ѽ҉ᶬḳ℠ <vtol@gmx.net> wrote:
> Thank you for the instant response.
>
>>
>> Wireguard does not mess with the DNS (afaik) so whatever is already
>> configured on the client is used.
>>
>
> Had hoped there would a way for the clients to utilize the endpoint node's
> DNS resolver.
>
>
There are many ways to do that. You could setup post-up scripts that modify
resolv.conf when the wg interface is up. You could run a caching dns server
on your lan that talks to your gateway dns resolver.
>> If you want to route ipv4 traffic of "clients" through your "server"
>> (using quotes here because wireguard is peer to peer, so it does not really
>> makes sense to say that), you probably need to enable ipv4 forwarding in
>> the kernel, and have postrouting rules that look like "iptables -t nat -A
>> POSTROUTING -o eth0 -j MASQUERADE".
>>
>
> forwarding is enabled in the kernel. Currently I am trying to set it up
> with the name space solution (https://www.wireguard.com/netns/) which
> perhaps do not require iptable rules, at least there is no mentioning of it.
>
I have not played with netns, so I cannot comment on that.
>
> Being a of peer-to-peer concept WG is then not really suited as VPN
> gateway?
>
>
It certainly is suited for tunneling all traffic through the tunnel. There
are a few blog posts around describing how to do this.
[-- Attachment #2: Type: text/html, Size: 2619 bytes --]
next prev parent reply other threads:[~2018-05-07 13:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-07 11:21 ѽ҉ᶬḳ℠
[not found] ` <CAHLp1Yk-33m1X5nkoVA7ofA8=h7uTdXP9x+DWmFzHkxAhq-g_g@mail.gmail.com>
[not found] ` <586e6364-d143-2b9b-8ea0-940072a9db9a@gmx.net>
2018-05-07 13:23 ` Christophe-Marie Duquesne [this message]
2018-05-07 15:19 ` ѽ҉ᶬḳ℠
2018-05-07 13:26 ` Kalin KOZHUHAROV
2018-05-07 17:43 ` ѽ҉ᶬḳ℠
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='CAHLp1YmAf+hD+iHD+cZPorqMp-m=Aw_nJ5E2TcQYrXt-y7FZNQ@mail.gmail.com' \
--to=chmd@chmd.fr \
--cc=vtol@gmx.net \
--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).