Development discussion of WireGuard
 help / color / mirror / Atom feed
From: sopium <sopium@mysterious.site>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>,
	"wireguard" <wireguard@lists.zx2c4.com>
Subject: Re: Some questions about the protocol
Date: Mon, 20 Mar 2017 14:06:13 +0900	[thread overview]
Message-ID: <15aea1bc5c3.c2181619229336.1203334027395810585@mysterious.site> (raw)
In-Reply-To: <CAHmME9p8kMshYw0A0v7ibY_jeNbMDLX5TE1+r0e02j+28kk8Dg@mail.gmail.com>

Hi,

Thanks for the reply. Some more questions.

The most tricky one first:

Do we send back keep-alive packets in response to keep-alive packets?
[No?] If so, they will ping-pong indefinitely, and persistent
keep-alive seems unnecessary. If not, do we send keep-alive packets in
response to persistent keep-alive packets? [Yes?] Then we need to
distinguish these two different types of keep-alive?

And,

2017-03-16 0:34 GMT+08:00 Jason A. Donenfeld <Jason@zx2c4.com>:
> [...]
>> * Shall we start handshake in case the _previous_ session is not
>>   alive, or too old? My guess is NO?
>
> I'm not sure I understand your question. Could you rephrase? Here's
> some text that might clarify things possibly:

[Not a question] I was thinking of these timers as tied to individual
sessions. It all makes sense if they are tied to the peer.

>> * When padding packets, how to avoid getting larger than MTU,
>>   because we don't seem to know the MTU?
>
> You know the MTU of the WireGuard interface, and so you pad packets to
> fit into that. You can query this from the TUN device.
>
> WireGuard currently doesn't do per-peer-endpoint PMTU, but I'm working
> on this, and I'll update you when this is worked out.

Since a WireGuard interface can have multiple peers, some may have
a smaller MTU than the interface MTU?

Regards,
Sopium

  reply	other threads:[~2017-03-20  5:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-15  3:25 sopium
2017-03-15  5:52 ` sopium
2017-03-15 16:34 ` Jason A. Donenfeld
2017-03-20  5:06   ` sopium [this message]
2017-03-20 15:18     ` 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=15aea1bc5c3.c2181619229336.1203334027395810585@mysterious.site \
    --to=sopium@mysterious.site \
    --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 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).