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: crypto routing with subnets?
Date: Fri, 20 Oct 2017 13:06:03 -0500	[thread overview]
Message-ID: <20171020180603.GA24912@wolff.to> (raw)
In-Reply-To: <CAHmME9rf2+S_pJqpGPPq+BXzMWTVyF92W2bVT904teHhVhJHoQ@mail.gmail.com>

On Fri, Oct 20, 2017 at 20:02:43 +0200,
  "Jason A. Donenfeld" <Jason@zx2c4.com> wrote:
>Hi Bruno,
>
>Fortunately the inquires of this email are things that you could
>figure out simply by trying, so if you want to learn-by-doing, you can
>stop reading here and finish reading afterward.

I'm doing that too. Though I can't test the full set up right now as I 
can't safely change the router firmware until I get home.

>
>Here are the solutions:
>
>1. A peer is its public key, which means you can't have two different
>peers with the same key, since they'd be the same peer. In essence
>you're asking for a==a&&a!=a, which is always false.

I mostly wanted to make sure I had a correct mental model for how this 
worked. It seemed like it had to be that way.

>2. Traffic will always go to the most specific route, which means the
>/32 will take precedence over the /16.

For this one, I was a bit worried that it might work sometimes, but have 
problems later as I couldn't find an explicit answer in the documentation 
(I might have missed it.) saying it worked like normal network routing. The 
examples I saw were all disjoint networks.

Thank you for the clarifications.

  reply	other threads:[~2017-10-20 18:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-20 17:39 crypto routing with subnets? Bruno Wolff III
2017-10-20 18:02 ` Jason A. Donenfeld
2017-10-20 18:06   ` Bruno Wolff III [this message]
2017-10-20 18:15     ` Jason A. Donenfeld

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=20171020180603.GA24912@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.