From: Bruno Wolff III <bruno@wolff.to>
To: Baptiste Jonglez <baptiste@bitsofnetworks.org>
Cc: wireguard@lists.zx2c4.com
Subject: Re: [WireGuard] Using wireguard link as a proxy?
Date: Fri, 22 Jul 2016 04:09:13 -0500 [thread overview]
Message-ID: <20160722090913.GA8383@wolff.to> (raw)
In-Reply-To: <20160722081821.GA11505@lud.polynome.dn42>
On Fri, Jul 22, 2016 at 10:18:21 +0200,
Baptiste Jonglez <baptiste@bitsofnetworks.org> wrote:
>
>Yes, the notion of "immediate next destinaton" does not make sense for
>Wireguard. It encapsulates plain IP, not Ethernet.
I thought that the next IP address might have been available for wireguard
to see as the information seems to be available for routing. But as you
mention below and I realized, that doesn't help with the return packets
since they can have (almost) any source address.
>You need "allowed ips 0.0.0.0/0" here. Your situation is just a regular
>client/server tunneling setup, there's nothing special about "proxying",
>whatever that means.
Yeah I realized that when thinking about this some more. "Proxy" in this
case means source nat will be used on the outgoing packets.
Thanks.
next prev parent reply other threads:[~2016-07-22 9:09 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 [this message]
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
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=20160722090913.GA8383@wolff.to \
--to=bruno@wolff.to \
--cc=baptiste@bitsofnetworks.org \
--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.