Development discussion of WireGuard
 help / color / mirror / Atom feed
From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: ae <aeforeve@mail.ru>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>,
	Roelf Wichertjes <roelf@roelf.org>
Subject: Re: Re[2]: problem wireguard + ospf + unconnected tunnels
Date: Mon, 10 Jul 2017 19:09:25 +0200	[thread overview]
Message-ID: <CAHmME9rBDRRnQ1z4+OFRrYjB5c+01oDAqxzdipx9TH4exhdg+w@mail.gmail.com> (raw)
In-Reply-To: <1499706363.749987194@f388.i.mail.ru>

On Mon, Jul 10, 2017 at 7:06 PM, ae <aeforeve@mail.ru> wrote:
> yes - work
Great to hear! This will be a part of the next snapshot.

> + Pair of missing functionality - which I lacked when replacing with wireguard
>
> 1) src addr tunnel
What is this? Can you elaborate on what you mean?

> 2) work in only preshared crypto
WireGuard has a preshared-key mode, but it's in addition to the normal
EC-based crypto, not instead of. Welcome to the future!

  reply	other threads:[~2017-07-10 16:51 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-03 21:09 ae
2017-07-04 15:55 ` Roelf "rewbycraft" Wichertjes
2017-07-04 17:10   ` Re[2]: " ae
2017-07-07 15:08     ` Roelf "rewbycraft" Wichertjes
2017-07-07 15:47       ` Re[2]: " ae
2017-07-10  0:46       ` Jason A. Donenfeld
2017-07-10 17:06         ` Re[2]: " ae
2017-07-10 17:09           ` Jason A. Donenfeld [this message]
2017-07-10 17:26             ` Re[4]: " ae
2017-07-08 14:21 ` Indefinite queuing for unconnected peers (Was: problem wireguard + ospf + unconnected tunnels) Baptiste Jonglez
2017-07-08 18:51   ` Roelf "rewbycraft" Wichertjes
2017-07-10  0:53   ` 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=CAHmME9rBDRRnQ1z4+OFRrYjB5c+01oDAqxzdipx9TH4exhdg+w@mail.gmail.com \
    --to=jason@zx2c4.com \
    --cc=aeforeve@mail.ru \
    --cc=roelf@roelf.org \
    --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).