Ask Your Question

batteryworm's profile - activity

2023-01-20 20:15:48 +0000 received badge  Taxonomist
2021-06-25 08:29:43 +0000 received badge  Famous Question (source)
2020-04-11 07:40:41 +0000 received badge  Famous Question (source)
2020-01-31 16:45:07 +0000 received badge  Notable Question (source)
2020-01-31 16:45:07 +0000 received badge  Popular Question (source)
2019-12-19 16:37:24 +0000 received badge  Notable Question (source)
2019-12-19 16:37:24 +0000 received badge  Popular Question (source)
2019-11-29 04:29:08 +0000 received badge  Famous Question (source)
2019-11-29 04:29:08 +0000 received badge  Notable Question (source)
2019-11-29 04:29:08 +0000 received badge  Popular Question (source)
2019-07-08 12:20:27 +0000 commented answer Receiver sends window update instead of DUP ACK

Thanks for asking. No, the issue is still unresolved. Both sender and receiver are running Linux. Sender side is by defa

2019-07-01 15:33:00 +0000 commented answer Receiver sends window update instead of DUP ACK

Thanks for your comment. Really appreciate it. We have asked sysadmin from receiver side about their implementation of T

2019-06-30 14:11:41 +0000 commented question Receiver sends window update instead of DUP ACK

A couple of other things to take note. Sender side tcpdump is taken at server OS level hence you see large MTU sizes,

2019-06-30 14:05:09 +0000 commented question Receiver sends window update instead of DUP ACK

I am still trying to get the 3-way TCP handshake which happens hours before the segment of the capture that points to th

2019-06-29 19:11:14 +0000 commented question Receiver sends window update instead of DUP ACK

SACK is not enabled. https://www.dropbox.com/sh/akzfjk2nb7on9oc/AADePEu_WhCSnPqahPUDov3Ba?dl=0 I have removed data field

2019-06-29 17:35:50 +0000 commented question Reason behind TCP RST from Client

Thanks for your comments. We have been trying to get the pcap from the other side but no response so far. Will update if

2019-06-29 17:32:24 +0000 asked a question Receiver sends window update instead of DUP ACK

Receiver sends window update instead of DUP ACK I have an issue whereby sender sends a bursty chunk of data across a WAN

2019-06-13 16:36:59 +0000 edited question Reason behind TCP RST from Client

Reason behind TCP RST from Client I need someone to help me interpret what is going on with the tcpdump I have - this is

2019-06-13 16:23:10 +0000 received badge  Editor (source)
2019-06-13 16:23:10 +0000 edited question Reason behind TCP RST from Client

Reason behind TCP RST from Client I need someone to help me interpret what is going on with the tcpdump I have - this is

2019-06-13 16:00:10 +0000 asked a question Reason behind TCP RST from Client

Reason behind TCP RST from Client I need someone to help me interpret what is going on with the tcpdump I have - this is

2019-05-18 11:34:06 +0000 marked best answer Why no data flow after TCP 3 way handshake?

I have an application that uses API to connect to server separated by a WAN. The problem is that it can establish a 3 way TCP handshake, but after that could not connect at the API level and after some time (20 seconds), the session disconnects. A tcpdump is taken at the client end who initiates the connection; at the same time a tcpdump is taken at the server end.

  1. At the client end, we can see client sending SYN, then receiving SYN-ACK from the server, and client sends ACK. Subsequent to this TCP session establishment, client then sends data (32 bytes) with PUSH, ACK. But there is no response from server. After 300 ms, client retransmit the data packet (same packet with 32 bytes) ie. retransmit. Again no response from server. After 600ms, client retransmit same data packet. No response from server. After 1.2 seconds, client retransmit; no response from server. This goes on for another few times, after about 11 seconds, client sends a RST to server; no response from server. Again client sends RST to server and no response. This repeats several time. Until finally at about 20 seconds, client receives RST from server.
  2. At the server end, we can see the SYN packet from client. Server response with SYN-ACK. Then server receives ACK from client so the TCP 3 way handshake is established. Subsequent to this server does not receive any more packets from client. After 20 seconds, server sends RST to client. What causes this behaviour?
2019-05-18 11:34:06 +0000 received badge  Scholar (source)
2019-05-18 11:32:41 +0000 commented answer Why no data flow after TCP 3 way handshake?

Thanks for your suggestions. A call to Company B network and server admin resolved the issue. It was due to a wrong rout

2019-05-16 15:47:32 +0000 commented answer Why no data flow after TCP 3 way handshake?

Just to add. I took a closer look at company B pcap. Noticed at the MAC layer the server seems to be communicating to tw

2019-05-16 15:23:45 +0000 commented answer Why no data flow after TCP 3 way handshake?

To clarify, this is not a HTTP protocol. It is a proprietary protocol using port 23027. I will attempt to describe the i

2019-05-16 15:23:02 +0000 received badge  Rapid Responder (source)
2019-05-16 15:23:02 +0000 answered a question Why no data flow after TCP 3 way handshake?

To clarify, this is not a HTTP protocol. It is a proprietary protocol using port 23027. I will attempt to describe the i

2019-05-16 14:46:42 +0000 asked a question Why no data flow after TCP 3 way handshake?

Why no data flow after TCP 3 way handshake? I have an application that uses API to connect to server separated by a WAN.