summaryrefslogtreecommitdiffhomepage
path: root/src/timers.c
diff options
context:
space:
mode:
authorJason A. Donenfeld <Jason@zx2c4.com>2016-07-08 14:26:25 +0200
committerJason A. Donenfeld <Jason@zx2c4.com>2016-07-08 14:28:15 +0200
commitfcd889b205f41901b822f768f461e3974f48b5f2 (patch)
tree2b8c876dadf737d19f10f3a1f8d66989b2379ce4 /src/timers.c
parentd6c566c92ac3f21c75301a540da275c87ea4b745 (diff)
persistent keepalive: start sending immediately
Rather than only start sending the persistent keepalive packets when the device first sends data, this changes it to send the packets immediately on `ip link set up`. This makes things generally seem more stateless, since the administrator does not have to manually ping the endpoint. Of course, if you have a lot of peers and all of them have persistent keepalive enabled, this could cause a lot of unwanted immediate traffic. On the other hand, if all of those peers are at some point going to be sending packets, this would happen anyway. I suppose the moral of the story is that persistent keepalive is a feature really just for clients behind NAT, not for servers, and it should be used sparingly, which is why we've set it off by default in the first place. Signed-off-by: Jason A. Donenfeld <Jason@zx2c4.com>
Diffstat (limited to 'src/timers.c')
0 files changed, 0 insertions, 0 deletions