Hi Björn!
Sorry for the late reply, I was on vacation.
You are correct, keep-alives fell victim to the upgrade to Tokio 1.0
and then we forgot to bring it back. I have re-opened the original
issue[0] with an aim to fix it in the next release.
Apologies and cheers,
Martin
[0]: https://github.co
Yep, that’s the workaround I’ve deployed, more frequent refreshes and this
helps since fw state info does not timeout.
I had a pretty long refresh time set before (1h) but since I have Routinator
refresh timer setup 1h it doesn’t really matter if I decrease the RTR refresh
timer.
From looking a
In some early lab testing I did, I noticed that RTR sessions were often
resetting every 10 minutes.
The reason I discerned was there was an intervening firewall which must've
had a 10 minute auto-flush of stale state info.
Rather than trying to fight a losing battle with firewall folks (also with
p
Hello,Did something change with the handling of tcp keepalives between version 0.8.2 and 0.10.0?I recently upgraded one of two servers to 0.10.0 and after the upgrade I don’t see keepalives which I do from the 0.8.2 server (and previously, before the upgrade, from the upgraded server).Same configur
