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=-5.3 required=3.0 tests=BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS, USER_AGENT_SANE_1 autolearn=no 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 CAB7EC4332B for ; Mon, 4 Jan 2021 12:40:57 +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 5CA79207AE for ; Mon, 4 Jan 2021 12:40:57 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 5CA79207AE Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=osk.ch Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=wireguard-bounces@lists.zx2c4.com Received: by krantz.zx2c4.com (ZX2C4 Mail Server) with ESMTP id fddc7164; Mon, 4 Jan 2021 12:28:37 +0000 (UTC) Received: from mail.osk.ch (dynamic.wline.6rd.res.cust.swisscom.ch [2a02:1205:5052:8220:20f:feff:fe92:5373]) by krantz.zx2c4.com (ZX2C4 Mail Server) with ESMTPS id d61db118 (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256:NO) for ; Sun, 3 Jan 2021 21:43:57 +0000 (UTC) Received: from server.osk.ch (localhost [127.0.0.1]) by mail.osk.ch (8.14.4/8.14.4/Debian-8+deb8u2) with ESMTP id 103Lsfme024330 for ; Sun, 3 Jan 2021 22:54:41 +0100 Received: (from osk@localhost) by server.osk.ch (8.14.4/8.14.4/Submit) id 103Lsfs6024329 for wireguard@lists.zx2c4.com; Sun, 3 Jan 2021 22:54:41 +0100 X-Authentication-Warning: server.osk.ch: osk set sender to wg@osk.ch using -f Date: Sun, 3 Jan 2021 22:54:41 +0100 From: Chris Osicki To: WireGuard mailing list Subject: WG default routing Message-ID: <20210103215441.GA24251@server> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-message-flag: Using Microsoft software might be a security risk User-Agent: Mutt/1.5.23 (2014-03-12) X-Greylist: inspected by milter-greylist-4.5.11 (mail.osk.ch [127.0.0.1]); Sun, 03 Jan 2021 22:54:41 +0100 (CET) for IP:'127.0.0.1' DOMAIN:'localhost' HELO:'server.osk.ch' FROM:'wg@osk.ch' RCPT:'' X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.11 (mail.osk.ch [127.0.0.1]); Sun, 03 Jan 2021 22:54:41 +0100 (CET) X-Mailman-Approved-At: Mon, 04 Jan 2021 13:28:34 +0100 X-BeenThere: wireguard@lists.zx2c4.com X-Mailman-Version: 2.1.30rc1 Precedence: list List-Id: Development discussion of WireGuard List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: wireguard-bounces@lists.zx2c4.com Sender: "WireGuard" Hi I am quite new to wireguard, moving after years of OpenVPN, and found it simple and _really good_. One thing, however, makes me wonder. Why WG tries always to take over all my routing? My first try was with wg-quick, and noticed all my traffic went through the WG-VPN connection. It escapes me why. What is the idea behind this policy? On my Linux boxes it's not a problem, I don't have to use wg-quick and with few lines of bash in a script I have what I need. I have root. On my Android devices I don't have root, and I cannot change anything in routing etc. Why don't you provide an option to specify which net to route which way? Regards, Chris