24 Bře
2024
24 Bře
'24
19:11
On 3/24/24 17:45, Randy Bush wrote:
omg!
it's shipped by default not being able to run reliably on the internet
and has no big "before you open this" warning on the box? it has cost
me days, and cost other folk hours.
If you enabled debug logging, you would see the connection is closed due to IO timeout.
A high timeout value has other disadvantages. That's why it's configurable!
i am not positive this is the key question as my tcp
fu is a bit rusty.
but why did seattle send the FIN at 219, 10% through the file?
I have experienced the same some time ago and I think this is what you
need to tune:
https://www.knot-dns.cz/docs/3.3/singlehtml/#tcp-io-timeout
i really appreciate the pointer and i have adjusted `tcp-io-timeout:
2000`, as i see no advice on tuning it to run on the internet.
randy, now wondering what other traps await
--