From: Matthias Urlichs <matthias@urlichs.de>
To: wireguard@lists.zx2c4.com
Subject: Re: Getting IPv6 route advertisements to work over WG
Date: Mon, 27 Aug 2018 16:55:41 +0200 [thread overview]
Message-ID: <f67cb9ce-70d0-0b2c-64b7-04b3c0397702@urlichs.de> (raw)
In-Reply-To: <AM5PR0802MB2450F5F2541FA58DF48E5D28FF0B0@AM5PR0802MB2450.eurprd08.prod.outlook.com>
On 27.08.2018 16:46, Riccardo Paolo Bestetti wrote:
> The tunnel could be initially established with no tunnel addresses,
It could also be initially established with one non-forwarded tunnel
address, allowing you to converse through the tunnel with standard
tools, and without adding unnecessary complexity to WG.
Also, keep in mind that you need an initial off-link transaction anyway,
to exchange public keys. You can exchange whatever else needs exchanging
at the same time.
--
-- Matthias Urlichs
next prev parent reply other threads:[~2018-08-27 14:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-27 12:14 Getting IPv6 route advertisements to work over WG Roman Mamedov
2018-08-27 13:32 ` netravnen
2018-08-27 13:53 ` Roman Mamedov
2018-08-27 14:46 ` Riccardo Paolo Bestetti
2018-08-27 14:55 ` Matthias Urlichs [this message]
2018-08-27 21:14 ` StarBrilliant
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=f67cb9ce-70d0-0b2c-64b7-04b3c0397702@urlichs.de \
--to=matthias@urlichs.de \
--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).