All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: Norman Shulman <norman.shulman@n-dimension.com>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: [WireGuard] WireGuard cryptokey routing
Date: Fri, 15 Jul 2016 13:51:17 +0200	[thread overview]
Message-ID: <CAHmME9py-ZGquBVCRckCJfy0gQLD1hNGx9fqQ57XGJSHu8Ns5Q@mail.gmail.com> (raw)
In-Reply-To: <CANQAqMX0ywXN0vTxmeZXLYL7kuB0By-18yN9Kj4=_sHGRuSooA@mail.gmail.com>

On Thu, Jul 14, 2016 at 11:16 PM, Norman Shulman
<norman.shulman@n-dimension.com> wrote:
> Sorry if this sounds too theoretical. I'm just trying to understand the
> cryptokey routing well enough to determine if it's suitable for our use. The
> main problem I have is understanding how you can base routing on
> non-routable addresses, which are not unique.

I don't think it's productive for either of us for me to continue
answering questions posed in this form. How about instead you write
down an example network layout ("Subnet A is 10.2.3.0/24, Subnet B
is...") and then present a problem you'd like to solve with WireGuard
but are having trouble figuring out how.

      reply	other threads:[~2016-07-15 11:50 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CANQAqMXqQv_MkEsLSuSHNVqHGJuy6yVHhVP4mM6v3x+5iVbVqA@mail.gmail.com>
     [not found] ` <CAHmME9rXYm3yV0j5pW3yH59j-C9S=6X8-6OY+b=dkuRq7Vpzvw@mail.gmail.com>
     [not found]   ` <CANQAqMX8Bf9taS+VgRYnGwuOoJcG3PL8PNmyOK66O3pHjP6VBw@mail.gmail.com>
     [not found]     ` <CAHmME9rRHgEtsJ8F-4UrzZMwOs43T24Jq+mUHO91-oimQXXjwg@mail.gmail.com>
     [not found]       ` <CANQAqMV=QeCG9BPvPpaCAu56a+mNi_7sNvhDL=_i4N7WFY1=Ng@mail.gmail.com>
     [not found]         ` <CAHmME9qr2H=4Qdzx9Kz4=op-O-yzum0+hJWvazHZ_K7ex05ncQ@mail.gmail.com>
2016-07-05 16:34           ` [WireGuard] Fwd: WireGuard cryptokey routing Jason A. Donenfeld
2016-07-05 18:05           ` [WireGuard] " Norman Shulman
2016-07-05 19:06             ` Jason A. Donenfeld
2016-07-05 19:09               ` Norman Shulman
2016-07-05 19:11                 ` Jason A. Donenfeld
2016-07-06 15:31                   ` Norman Shulman
2016-07-06 15:37                     ` Jason A. Donenfeld
2016-07-06 15:48                     ` Baptiste Jonglez
2016-07-07 16:15                       ` Norman Shulman
2016-07-07 16:18                         ` Jason A. Donenfeld
2016-07-14 21:16                           ` Norman Shulman
2016-07-15 11:51                             ` Jason A. Donenfeld [this message]

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=CAHmME9py-ZGquBVCRckCJfy0gQLD1hNGx9fqQ57XGJSHu8Ns5Q@mail.gmail.com \
    --to=jason@zx2c4.com \
    --cc=norman.shulman@n-dimension.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.