Conversation

Notices

1. Embed this notice
   niconiconi (niconiconi@mk.absturztau.be)'s status on Tuesday, 29-Oct-2024 00:41:49 JST niconiconi

   nf_conntrack has several timeout setting, each for entries of different TCP states [...] default timeout for established state conntrack entries is 423000 s (5 days!). Possible reason for so large a value may be: TCP/IP specification allows established connection stays idle for infinite long time (but still alive)TIL :woozy_baa:

   • Haelwenn /элвэн/ :triskell: likes this.
   • Embed this notice
     Haelwenn /элвэн/ :triskell: (lanodan@queer.hacktivis.me)'s status on Tuesday, 29-Oct-2024 00:49:24 JST Haelwenn /элвэн/ :triskell:

     in reply to
     @niconiconi Makes me wonder if that includes not answering back, 5 days of pure idle… it's a lot but hours could make sense for like slow sensors or syslog where re-establishing a connection everytime would be kind of annoying.
     
     While not answering back… max of like ~10 minutes would be as far as I'd go (like ping timeout on IRC being typically 250 seconds and forgot for SSH but there's a similar thing).