From: Reid Rankin <reidrankin@gmail.com>
To: John Smith <dingrite@gmail.com>
Cc: wireguard@lists.zx2c4.com
Subject: Re: [feature request] Randomize PersistentKeepalive
Date: Tue, 25 Feb 2020 00:14:22 -0500 [thread overview]
Message-ID: <CAMaqUZ1r7Y_57bUYs=D_EoACbzA9uvkywTMEhUsMa1QgT_X9UA@mail.gmail.com> (raw)
In-Reply-To: <CA+5JoNrd7dNRQv+y7-wBw1denTt9GKnvF3S1R-FwgYixauMC=w@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1342 bytes --]
Won't help -- a keepalive is by definition the minimum possible size frame.
That means not just that it's a predictable size, but that everything that
size must be a keepalive, randomized interval or not.
To get the kind of effect you're looking for, you'd need to send actual
dummy data -- which, incidentally, you can totally do no problem just by
making sure you're sending packets from an IP that isn't on the AllowedIPs
list on the other side. That will always cause the payload to be silently
dropped on the floor before it even hits the rest of the networking stack,
and with resource usage comparable to that of keepalives.
--Reid
On Mon, Feb 24, 2020 at 7:49 PM John Smith <dingrite@gmail.com> wrote:
> There are some applications where you do not want a listener to know that
> a channel is being kept alive and no information is being transmitted.
>
> Perhaps the ideal solution would be to add an option to the wg tool to
> send a keepalive packet, preferably of arbitrary size within some range. A
> script could then be used to keep the channel alive in a manner. Would be
> cleaner than sending something else through that may require further action
> by the peer.
> _______________________________________________
> WireGuard mailing list
> WireGuard@lists.zx2c4.com
> https://lists.zx2c4.com/mailman/listinfo/wireguard
>
[-- Attachment #1.2: Type: text/html, Size: 1966 bytes --]
[-- Attachment #2: Type: text/plain, Size: 148 bytes --]
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard
prev parent reply other threads:[~2020-02-25 5:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-24 6:21 John Smith
2020-02-25 5:14 ` Reid Rankin [this message]
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='CAMaqUZ1r7Y_57bUYs=D_EoACbzA9uvkywTMEhUsMa1QgT_X9UA@mail.gmail.com' \
--to=reidrankin@gmail.com \
--cc=dingrite@gmail.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).