From: Bruno Wolff III <bruno@wolff.to>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: [WireGuard] Using wireguard link as a proxy?
Date: Fri, 22 Jul 2016 10:14:58 -0500 [thread overview]
Message-ID: <20160722151458.GA14212@wolff.to> (raw)
In-Reply-To: <CAHmME9rX828zTOjCvcHAQgNxofmDxU0WpZcgqPTTMX2v-ZKmgA@mail.gmail.com>
On Fri, Jul 22, 2016 at 14:42:52 +0200,
"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
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.
next prev parent reply other threads:[~2016-07-22 15:14 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-21 20:57 [WireGuard] Using wireguard link as a proxy? Bruno Wolff III
2016-07-22 8:18 ` Baptiste Jonglez
2016-07-22 9:09 ` Bruno Wolff III
2016-07-22 9:32 ` Baptiste Jonglez
2016-07-22 11:32 ` Bruno Wolff III
2016-07-22 12:42 ` Jason A. Donenfeld
2016-07-22 15:14 ` Bruno Wolff III [this message]
2016-07-22 15:30 ` Jason A. Donenfeld
2016-07-22 16:13 ` Bruno Wolff III
2016-07-22 18:05 ` Bruno Wolff III
2016-07-23 16:36 ` Bruno Wolff III
2016-07-23 17:25 ` Bruno Wolff III
2016-07-25 12:57 ` Jason A. Donenfeld
2016-07-25 15:40 ` Bruno Wolff III
2016-07-22 15:35 ` Quan Zhou
2016-07-22 16:02 ` Bruno Wolff III
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=20160722151458.GA14212@wolff.to \
--to=bruno@wolff.to \
--cc=Jason@zx2c4.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.