I've been able to reproduce this issue in Lucid and I can confirm that reverting the following commits actually fixes the problem:
d77028ffe1a3d6eb5f57c5e5ea87cbfc4ee05eb1 "net: check net.core.somaxconn sysctl values" 2dc19ed6338a27a78c7a9d47d311ae4ac5302c83 "sysctl net: Keep tcp_syn_retries inside the boundary"
So, although the fix proposed by Tyler in comment #3 could be the correct fix for this regression, it has been decided to actually revert the offending commits (as usual when a regression is found in an SRU).
I've been able to reproduce this issue in Lucid and I can confirm that reverting the following commits actually fixes the problem:
d77028ffe1a3d6e b5f57c5e5ea87cb fc4ee05eb1 "net: check net.core.somaxconn sysctl values" 78c7a9d47d311ae 4ac5302c83 "sysctl net: Keep tcp_syn_retries inside the boundary"
2dc19ed6338a27a
So, although the fix proposed by Tyler in comment #3 could be the correct fix for this regression, it has been decided to actually revert the offending commits (as usual when a regression is found in an SRU).