https://www.fromdual.com/blog/huge-amount-of-time-wait-connections/comment-844/Recent content in Thank you for the article. on FromDual GmbHHugoen-GBoli.sennhauser@fromdual.com (Oli Sennhauser)oli.sennhauser@fromdual.com (Oli Sennhauser)© FromDual GmbHMon, 23 Sep 2013 19:40:33 +0200https://www.fromdual.com/blog/huge-amount-of-time-wait-connections/comment-844/Mon, 23 Sep 2013 19:40:33 +0200oli.sennhauser@fromdual.com (Oli Sennhauser)https://www.fromdual.com/blog/huge-amount-of-time-wait-connections/comment-844/<p>Thank you for the article. Sorry to nitpick. My colleague pointed out if the local port range is 32768 – 61000, that there are 28233 available ports, not 28232.</p> <p>It may also be worth mentioning the difference between FIN TIMEOUT (/proc/sys/net/ipv4/tcp_fin_timeout) and the TIMEWAIT length which is hard-coded to 60s in the linux kernel.</p> <p>This question contains some good pointers and the answer contains a little program in C that you can compile and use to see how long the timeout is: <a href="http://unix.stackexchange.com/questions/17218/how-long-is-a-tcp-local-socket-address-that-has-been-bound-unavailable-after-clo">http://unix.stackexchange.com/questions/17218/how-long-is-a-tcp-local-socket-address-that-has-been-bound-unavailable-after-clo</a></p> <p>A similar article: <a href="http://www.krenel.org/tcp-time_wait-and-ephemeral-ports-bad-friends/">http://www.krenel.org/tcp-time_wait-and-ephemeral-ports-bad-friends/</a></p>