On Mon, Aug 21, 2017 at 3:13 PM, David Laight <david.lai...@aculab.com> wrote: > From: Akshat Kakkar >> Sent: 18 August 2017 10:14 >> On Thu, Aug 17, 2017 at 5:06 PM, Eric Dumazet <eric.duma...@gmail.com> wrote: >> > On Thu, 2017-08-17 at 14:35 +0530, Akshat Kakkar wrote: >> > >> >> I upgraded to 4.4 but still experiencing same issue. >> >> Please help. >> > >> > Still too old kernel, shoot again ;) >> > >> > >> >> >> Sorry but that's the maximum I can try as of now as its the LT version. > > You should be able to build a current kernel and run it with your > existing user space. > > David >
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??
