holds good - that the tcp stack needs to update the
saved TSval to that of the latest SYN, right ?
Rgds,
Gopa.
On Wed, May 27, 2015 at 11:02 AM, Eric Dumazet wrote:
> On Wed, 2015-05-27 at 10:57 -0700, Eric Dumazet wrote:
>> On Wed, 2015-05-27 at 10:29 -0700, Gopakumar Choorakkot
Thanks Eric. I will give this a spin. The issue doesnt happen all the
time, I can keep the server running with this patch for a while and
observe if the issue resurfaces or not
Rgds,
Gopa.
On Wed, May 27, 2015 at 6:45 AM, Eric Dumazet wrote:
> On Wed, 2015-05-27 at 06:33 -0700, Eric Dumazet wrot
,
Gopa.
On Tue, May 26, 2015 at 11:23 PM, Eric Dumazet wrote:
> On Tue, 2015-05-26 at 23:12 -0700, Eric Dumazet wrote:
>> On Tue, 2015-05-26 at 22:47 -0700, Gopakumar Choorakkot Edakkunni wrote:
>> > All,
>> >
>> > The original query I had posted is here :
>
All,
The original query I had posted is here :
http://stackoverflow.com/questions/30414350/tcp-syn-ack-tsecr-not-matching-tsval-in-syn
.. The summary is that once in a while, the TSval in SYN is not what
is getting echoed in TSecr, and looks like something on amazon aws
side is very strict about t
All,
The original query I had posted is here :
http://stackoverflow.com/questions/30414350/tcp-syn-ack-tsecr-not-matching-tsval-in-syn
.. The summary is that once in a while, the TSval in SYN is not what
is getting echoed in TSecr, and looks like something on amazon aws
side is very strict about t
All,
The original query I had posted is here :
http://stackoverflow.com/questions/30414350/tcp-syn-ack-tsecr-not-matching-tsval-in-syn
.. The summary is that once in a while, the TSval in SYN is not what
is getting echoed in TSecr, and looks like something on amazon aws
side is very strict about t
All,
The original query I had posted is here :
http://stackoverflow.com/questions/30414350/tcp-syn-ack-tsecr-not-matching-tsval-in-syn
.. The summary is that once in a while, the TSval in SYN is not what
is getting echoed in TSecr, and looks like something on amazon aws
side is very strict about t
