From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: quanzhou822@gmail.com Received: from mail-yw0-f169.google.com (mail-yw0-f169.google.com [209.85.161.169]) by krantz.zx2c4.com (ZX2C4 Mail Server) with ESMTP id cff377c8 for ; Fri, 22 Jul 2016 15:33:18 +0000 (UTC) Received: by mail-yw0-f169.google.com with SMTP id j12so99468425ywb.2 for ; Fri, 22 Jul 2016 08:35:22 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: <20160722151458.GA14212@wolff.to> References: <20160721205742.GA10312@wolff.to> <20160722081821.GA11505@lud.polynome.dn42> <20160722090913.GA8383@wolff.to> <20160722093211.GA12311@lud.polynome.dn42> <20160722113212.GA17578@wolff.to> <20160722151458.GA14212@wolff.to> From: Quan Zhou Date: Fri, 22 Jul 2016 23:35:02 +0800 Message-ID: To: wireguard@lists.zx2c4.com Content-Type: multipart/alternative; boundary=94eb2c115f44b828bd05383b2ee2 Subject: Re: [WireGuard] Using wireguard link as a proxy? List-Id: Development discussion of WireGuard List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , --94eb2c115f44b828bd05383b2ee2 Content-Type: text/plain; charset=UTF-8 I happen to have a similar problem, using `AllowedIPs = 0.0.0.0/0` on both sides of a wireguard link works, but when I try to add more peers, all but one gets `(none)`. I know this is by design, but it would be sweet if I can manually set gateways within a wireguarded network. On Fri, Jul 22, 2016 at 11:14 PM, Bruno Wolff III wrote: > On Fri, Jul 22, 2016 at 14:42:52 +0200, > "Jason A. Donenfeld" wrote: > >> I usually do something like: >> >> wg set wg0 peer ABCD allowed-ips 0.0.0.0/0 >> ip route add 0/1 dev wg0 >> ip route add 128/1 dev wg0 >> > > The idea I am working on now is to use policy writing and rules, so that > packets sent to the proxy server are routed using the normal routing table > which includes the default route supplied by dhcp, but eveything else (well > not 127/8) uses an alternate routing table that has a default route through > wg0. This way I can use a fixed set up and not have to parse the routing > info setup after a wireless connection is made. > > I need to do some reading to get the details for creating routing tables > and rules for picking them, but expect this will work. > > _______________________________________________ > WireGuard mailing list > WireGuard@lists.zx2c4.com > http://lists.zx2c4.com/mailman/listinfo/wireguard > -- Regards, Quan Zhou +------------------------+ |pub [expires 2019-05-04]| |2C0C 4D88 E631 4C73 4C44| |CDE0 C0E 5470 1D2D 3F3EE| +------------------------+ |pub [revoked 2016-04-16]| |44D2 0307 1643 E80F 2E31| |F081 FAFA 6643 7F9F D46F| +------------------------+ |quanzhou822@gmail.com | |https://keybase.io/qzhou| +------------------------+ --94eb2c115f44b828bd05383b2ee2 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
I happen to have a similar problem, using `AllowedIPs =3D = 0.0.0.0/0` on both sides of a wireguard l= ink works, but when I try to add more peers, all but one gets `(none)`. I k= now this is by design, but it would be sweet if I can manually set gateways= within a wireguarded=C2=A0network.

On Fri, Jul 22, 2016 at 11:14 PM, Bruno Wolff III <= span dir=3D"ltr"><br= uno@wolff.to> wrote:
On Fri, Jul 22, 2016 at 14:42:52 +0200,
=C2=A0"Jason A. Donenfeld" <Jason@zx2c4.com> wrote:
I usually do something like:

wg set wg0 peer ABCD allowed-ips 0.0.0.0/0
ip route add 0/1 dev wg0
ip route add 128/1 dev wg0

 The idea I am working on now is to use policy writing and rules, so that pa= ckets sent to the proxy server are routed using the normal routing table wh= ich includes the default route supplied by dhcp, but eveything else (well n= ot 127/8) uses an alternate routing table that has a default route through = wg0. This way I can use a fixed set up and not have to parse the routing in= fo setup after a wireless connection is made.

I need to do some reading to get the details for creating routing tables an= d rules for picking them, but expect this will work.
<= div class=3D"h5">
_______________________________________________
WireGuard mailing list
WireGuard@li= sts.zx2c4.com
http://lists.zx2c4.com/mailman/listinfo/wireguard



--
=
--94eb2c115f44b828bd05383b2ee2--