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 <dingr...@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 >
_______________________________________________ WireGuard mailing list WireGuard@lists.zx2c4.com https://lists.zx2c4.com/mailman/listinfo/wireguard