Development discussion of WireGuard
 help / color / mirror / Atom feed
From: Roman Mamedov <rm@romanrm.net>
To: Matthias Urlichs <matthias@urlichs.de>
Cc: wireguard@lists.zx2c4.com
Subject: Re: Traffic on port 53 fails on LTE but works on WiFi
Date: Mon, 19 Nov 2018 21:02:11 +0500	[thread overview]
Message-ID: <20181119210211.107d225c@natsu> (raw)
In-Reply-To: <69b87340-f599-454a-3c46-7a153767e400@urlichs.de>

On Mon, 19 Nov 2018 09:54:38 +0100
Matthias Urlichs <matthias@urlichs.de> wrote:

> Redirecting port 53 to their DNS (presumably one close to their LTE
> endpoint) is reasonable, that should improve speed.

There is no justification to mess with user traffic like that.

If I specifically chose to use a specific DNS server, such as 1.1.1.1 (for its
privacy and non-tracking policies, however true or not), I should be allowed
to, and I should not have that redirected back to ISP's resolvers.

By redirecting or supporting redirection of DNS traffic you step down to the
level of oppressive censorship-states, for instance in "some countries" ISPs
do that (among other things), to prevent users from reading any content by
critiques and opponents of the country's dictator.

But, the overly-eager ISPs already got their dish served, in the form of
DNS-over-HTTPS (or TLS). They thought messing with DNS to "improve speed" was
innocent enough, but nope, so now they won't get to do any of that whatsoever.

As for improving speed on LTE, it is enough that the DHCP server gives you the
ISP's resolver close to your LTE endpoint. But the choice whether or not to
use it, should be left to the user.

-- 
With respect,
Roman
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard

  reply	other threads:[~2018-11-19 16:02 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-18 18:55 John
2018-11-19  4:26 ` Quan Zhou
2018-11-19  7:32 ` M. Dietrich
2018-11-19  8:40   ` John
2018-11-19  8:54   ` Matthias Urlichs
2018-11-19 16:02     ` Roman Mamedov [this message]
2018-11-19  9:57 ` Problem to load wireguard LKM in Archlinux Tosh
2018-11-19 15:04   ` John
2018-11-19 15:25 Traffic on port 53 fails on LTE but works on WiFi Jacob Schooley
2018-11-19 20:24 ` John

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=20181119210211.107d225c@natsu \
    --to=rm@romanrm.net \
    --cc=matthias@urlichs.de \
    --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).