From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-1.0 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_PASS autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 1A832C43441 for ; Mon, 19 Nov 2018 16:02:35 +0000 (UTC) Received: from krantz.zx2c4.com (krantz.zx2c4.com [192.95.5.69]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id 9B91020831 for ; Mon, 19 Nov 2018 16:02:34 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 9B91020831 Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=romanrm.net Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=wireguard-bounces@lists.zx2c4.com Received: from krantz.zx2c4.com (localhost [IPv6:::1]) by krantz.zx2c4.com (ZX2C4 Mail Server) with ESMTP id 365457a6; Mon, 19 Nov 2018 15:56:17 +0000 (UTC) Received: from krantz.zx2c4.com (localhost [127.0.0.1]) by krantz.zx2c4.com (ZX2C4 Mail Server) with ESMTP id 83682f9d for ; Mon, 19 Nov 2018 15:56:12 +0000 (UTC) Received: from len.romanrm.net (len.romanrm.net [91.121.75.85]) by krantz.zx2c4.com (ZX2C4 Mail Server) with ESMTP id 3e5cbc8c for ; Mon, 19 Nov 2018 15:56:12 +0000 (UTC) Received: from natsu (unknown [IPv6:fd39::e99e:8f1b:cfc9:ccb8]) by len.romanrm.net (Postfix) with SMTP id 9A76920394; Mon, 19 Nov 2018 16:02:11 +0000 (UTC) Date: Mon, 19 Nov 2018 21:02:11 +0500 From: Roman Mamedov To: Matthias Urlichs Subject: Re: Traffic on port 53 fails on LTE but works on WiFi Message-ID: <20181119210211.107d225c@natsu> In-Reply-To: <69b87340-f599-454a-3c46-7a153767e400@urlichs.de> References: <1542611942.d09p50zvb2.astroid@morple.none> <69b87340-f599-454a-3c46-7a153767e400@urlichs.de> X-Mailer: Claws Mail 3.11.1 (GTK+ 2.24.31; x86_64-pc-linux-gnu) MIME-Version: 1.0 Cc: wireguard@lists.zx2c4.com X-BeenThere: wireguard@lists.zx2c4.com X-Mailman-Version: 2.1.15 Precedence: list List-Id: Development discussion of WireGuard List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: wireguard-bounces@lists.zx2c4.com Sender: "WireGuard" On Mon, 19 Nov 2018 09:54:38 +0100 Matthias Urlichs 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