Where did the TCP reply disappear?
Five synchronized capture points followed one real TCP connection inside an isolated Linux lab. Switch routers to compare the two ends of the return path.
Capture point
Step 5 of 8
A matching SYN-ACK comes back
The service replies with the next client sequence number it expects. The returning packet passes through R2.
Evidence and sources
- Service egress
- Frame 6 · +191 µs
- Acknowledgment
- 2301309280 = client sequence + 1