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: Tue, 5 Jul 2016 21:11:43 +0200 [thread overview]
Message-ID: <CAHmME9pFhJoW+kFmJE7-acmb2q4=EqN+U+dJQ8GDEvBzN_=dRg@mail.gmail.com> (raw)
In-Reply-To: <CANQAqMWY=8WRbz9+bw11oUO2OAi-SFnHv=f+z5jQ0F1MYf5Ruw@mail.gmail.com>
On Tue, Jul 5, 2016 at 9:09 PM, Norman Shulman
<norman.shulman@n-dimension.com> wrote:
> How is this enforced?
Receiving, line 238 here:
https://git.zx2c4.com/WireGuard/tree/src/receive.c#n238
Sending, line 112 here:
https://git.zx2c4.com/WireGuard/tree/src/device.c#n112
> How does this scale?
The same way in which an ethernet network scales? One ethernet device
can have multiple IPs, but separate (unbonded) ethernet devices
generally do not share IPs.
next prev parent reply other threads:[~2016-07-05 19:08 UTC|newest]
Thread overview: 11+ 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 18:05 ` 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 [this message]
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
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='CAHmME9pFhJoW+kFmJE7-acmb2q4=EqN+U+dJQ8GDEvBzN_=dRg@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).