Disable reuse of TIME_WAIT sockets

[raja-grewal]

This pull request disable reuse of TIME_WAIT sockets for new outgoing connections as the safety of this feature is reliant on TCP timestamps which we have disabled.

TCP timestamps have been disabled since 01/04/2016 as per #1, that is, the very first pull request or issue on GitHub.

Note that this setting currently defaults to net.ipv4.tcp_tw_reuse=2 which permits reuse only for loopback connections. This is still broken as there are no associated timestamps to ensure the new connection is not a duplicate segment from an older connection.

Changes

Set sysctl net.ipv4.tcp_tw_reuse=0 setting.

Mandatory Checklist

• Legal agreements accepted. By contributing to this organisation, you acknowledge you have read, understood, and agree to be bound by these these agreements:

Terms of Service, Privacy Policy, Cookie Policy, E-Sign Consent, DMCA, Imprint

Optional Checklist

The following items are optional but might be requested in certain cases.

• I have tested it locally
• I have reviewed and updated any documentation if relevant
• I am providing new code and test(s) for it

[ArrayBolt3]

Looks good to me, merged into my arraybolt3/trixie branch.