On Mon, Aug 21, 2017 at 5:56 AM, Akshat Kakkar <akshat.1...@gmail.com> wrote: > > The issue is with tcp timestamp. When I am disabling it, things are > working fine but when I enable the issue re-occurs. However, I am not > seeing tcp timestamps on packet, even when it is enabled simply > because my client doesn't support it. > > But the question is, if I my client doesnt support timestamp , why > enabling timestamp on server side is creating an issue??
To help shed light on this, you could try collecting and dumping the nstat counters when the system is in the mode where it is not creating/accepting new connections, e.g.: nstat > /dev/null && sleep 10 && nstat The sleep interval would need to be long enough to cover a failing client connect attempt. It would also be helpful to gather a tcpdump trace over the interval, to see if the server is sending a RST, SYN+ACK, or nothing. neal
