On Wed, 2015-05-27 at 06:33 -0700, Eric Dumazet wrote:
The problem is in linux code itself. Please try the patch I sent ?
(On the client)
On the server, sorry for the typo.
diff --git a/net/ipv4/tcp_minisocks.c b/net/ipv4/tcp_minisocks.c
index
On Wed, 2015-05-27 at 00:09 -0700, Gopakumar Choorakkot Edakkunni wrote:
Hi Eric,
Thanks a lot for the response, and sorry about the 3-times-email, was
not sure whether majordomo accepted my subscription or not and hence
the retx :)
So if a sequence happens as below
1. Client sends the
On Wed, 2015-05-27 at 10:29 -0700, Gopakumar Choorakkot Edakkunni wrote:
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
Note that if the traffic on the server is
On Wed, 2015-05-27 at 10:57 -0700, Eric Dumazet wrote:
On Wed, 2015-05-27 at 10:29 -0700, Gopakumar Choorakkot Edakkunni wrote:
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
Doesnt seem so. This is the output from one of the servers I have
where I periodically hit this TSval != TSecr condition.
ubuntu@server:~$ sudo su
root@server:/home/ubuntu# sysctl net.ipv4.tcp_tw_recycle
net.ipv4.tcp_tw_recycle = 0
root@server:/home/ubuntu# sysctl net.ipv4.tcp_tw_reuse
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 eric.duma...@gmail.com wrote:
On Wed, 2015-05-27 at 06:33
On Wed, 2015-05-27 at 11:15 -0700, Gopakumar Choorakkot Edakkunni wrote:
Doesnt seem so. This is the output from one of the servers I have
where I periodically hit this TSval != TSecr condition.
ubuntu@server:~$ sudo su
root@server:/home/ubuntu# sysctl net.ipv4.tcp_tw_recycle
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
On Tue, 2015-05-26 at 22:47 -0700, Gopakumar Choorakkot Edakkunni wrote:
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
Hi Eric,
Thanks a lot for the response, and sorry about the 3-times-email, was
not sure whether majordomo accepted my subscription or not and hence
the retx :)
So if a sequence happens as below
1. Client sends the first SYN with some TSval X
2. Server responds SYN-ACK with TSecr X
3. The
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 :
http://stackoverflow.com/questions/30414350/tcp-syn-ack-tsecr-not-matching-tsval-in-syn
.. The summary is that
On Tue, 2015-05-26 at 23:23 -0700, 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
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
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
15 matches
Mail list logo
