All of lore.kernel.org
 help / color / mirror / Atom feed
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: Sat, 23 Jul 2016 12:25:53 -0500	[thread overview]
Message-ID: <20160723172553.GA6236@wolff.to> (raw)
In-Reply-To: <20160723163637.GA3426@wolff.to>

On Sat, Jul 23, 2016 at 11:36:37 -0500,
  Bruno Wolff III <bruno@wolff.to> wrote:
>The explanations for marking and policy routing aren't explicit about 
>how you need to handle the source address issue and why it happens, 
>though there are lots of mentions that there are problems related to 
>the source address.

You also need to turn off rp_filter on interfaces because packets coming 
from the tunnel can look like they should have come from the normal 
gateway and will get dropped locally.

  reply	other threads:[~2016-07-23 17:24 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
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 [this message]
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=20160723172553.GA6236@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.