Development discussion of WireGuard
 help / color / mirror / Atom feed
From: ѽ҉ᶬḳ℠ <vtol@gmx.net>
To: wireguard <wireguard@lists.zx2c4.com>
Subject: WG endpoint node exit to inet and DNS resolver
Date: Mon, 7 May 2018 13:21:17 +0200	[thread overview]
Message-ID: <c940ea93-e022-27ba-f906-783b0a7d3c1a@gmx.net> (raw)

[-- Attachment #1: Type: text/plain, Size: 1033 bytes --]

4.9.0-6-amd64 #1 SMP Debian 4.9.88-1 as WG endpoint node
WG 0.0.20180420-1
DHCP no
Firewall off (both server and client)
wg-quick not utilized

Which DNS resolver is utilized by the clients inside a WG tunnel, the 
client's resolver or the server's? And can this be tweaked in WG?

---

Clients are connecting to the endpoint node and subnets each end are 
reachable through the tunnel. The traffic to the inet from the WG 
however is not escaping via the server's default route. Added the IPS's 
gateway node (81.x.x.x) to the WG iface but that did not provide inet 
connection for the connected clients.

Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use 
Iface
0.0.0.0         81.x.x.x    0.0.0.0         UG    0      0 0 eth0
81.x.x.x    0.0.0.0         255.255.255.255 UH    0      0 0 wg0
192.168.120.0   0.0.0.0         255.255.255.0   U     0 0        0 wg0





[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4174 bytes --]

             reply	other threads:[~2018-05-07 11:18 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-07 11:21 ѽ҉ᶬḳ℠ [this message]
     [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
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=c940ea93-e022-27ba-f906-783b0a7d3c1a@gmx.net \
    --to=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).