Capture
Fast retransmission after duplicate ACKs · captured at the client · built for teaching and checked with tshark
Drag your capture here or open it with the button: it is read in your browser, never leaves your device and is not saved.
What is going on
- Fast retransmission:
- Duplicate ACK: , , ,
What Wireshark does not tell you
At packet 9 a piece is missing that was lost BEFORE reaching the capture point. If its resend arrives on a timeout and in order, from here it will look like a normal segment arriving late: such a retransmission can only be seen capturing at the sender.
| N.º | Time | Source | Destination | Proto | Info | Analysis |
|---|---|---|---|---|---|---|
| 1 | 0.000000 | 192.168.1.48 | 10.0.0.247 | DNS | ? blog.prueba.test (id 0x49f4) | |
| 2 | 0.017000 | 10.0.0.247 | 192.168.1.48 | DNS | NOERROR · blog.prueba.test → CNAME edge.blog.prueba.test, A 203.0.119.211 (id 0x49f4) | |
| 3 | 0.018000 | 192.168.1.48 | 203.0.119.211 | TCP | 52028 → 80 [SYN] Seq=0 Win=64240 Len=0 | |
| 4 | 0.023000 | 203.0.119.211 | 192.168.1.48 | TCP | 80 → 52028 [SYN, ACK] Seq=0 Ack=1 Win=64240 Len=0 | |
| 5 | 0.023100 | 192.168.1.48 | 203.0.119.211 | TCP | 52028 → 80 [ACK] Seq=1 Ack=1 Win=64240 Len=0 | |
| 6 | 0.023300 | 192.168.1.48 | 203.0.119.211 | HTTP | GET /login HTTP/1.1 (Host: blog.prueba.test) · 52028 → 80 [PSH, ACK] Seq=1 Ack=1 Win=64240 Len=86 | |
| 7 | 0.028300 | 203.0.119.211 | 192.168.1.48 | TCP | 80 → 52028 [PSH, ACK] Seq=1 Ack=87 Win=64240 Len=1000 | |
| 8 | 0.028400 | 192.168.1.48 | 203.0.119.211 | TCP | 52028 → 80 [ACK] Seq=87 Ack=1001 Win=64240 Len=0 | |
| 9 | 0.028700 | 203.0.119.211 | 192.168.1.48 | TCP | 80 → 52028 [PSH, ACK] Seq=2001 Ack=87 Win=64240 Len=1000 | Previous segment missing |
| 10 | 0.028800 | 192.168.1.48 | 203.0.119.211 | TCP | 52028 → 80 [ACK] Seq=87 Ack=1001 Win=64240 Len=0 | Duplicate ACK #1 |
| 11 | 0.029100 | 203.0.119.211 | 192.168.1.48 | TCP | 80 → 52028 [PSH, ACK] Seq=3001 Ack=87 Win=64240 Len=1000 | |
| 12 | 0.029200 | 192.168.1.48 | 203.0.119.211 | TCP | 52028 → 80 [ACK] Seq=87 Ack=1001 Win=64240 Len=0 | Duplicate ACK #2 |
| 13 | 0.029500 | 203.0.119.211 | 192.168.1.48 | TCP | 80 → 52028 [PSH, ACK] Seq=4001 Ack=87 Win=64240 Len=1000 | |
| 14 | 0.029600 | 192.168.1.48 | 203.0.119.211 | TCP | 52028 → 80 [ACK] Seq=87 Ack=1001 Win=64240 Len=0 | Duplicate ACK #3 |
| 15 | 0.029900 | 203.0.119.211 | 192.168.1.48 | TCP | 80 → 52028 [PSH, ACK] Seq=5001 Ack=87 Win=64240 Len=831 | |
| 16 | 0.030000 | 192.168.1.48 | 203.0.119.211 | TCP | 52028 → 80 [ACK] Seq=87 Ack=1001 Win=64240 Len=0 | Duplicate ACK #4 |
| 17 | 0.035000 | 203.0.119.211 | 192.168.1.48 | HTTP | HTTP/1.1 200 OK · 80 → 52028 [PSH, ACK] Seq=1001 Ack=87 Win=64240 Len=1000 | Fast retransmission |
| 18 | 0.035100 | 192.168.1.48 | 203.0.119.211 | TCP | 52028 → 80 [ACK] Seq=87 Ack=5832 Win=64240 Len=0 | |
| 19 | 0.035300 | 192.168.1.48 | 203.0.119.211 | TCP | 52028 → 80 [FIN, ACK] Seq=87 Ack=5832 Win=64240 Len=0 | |
| 20 | 0.040300 | 203.0.119.211 | 192.168.1.48 | TCP | 80 → 52028 [FIN, ACK] Seq=5832 Ack=88 Win=64240 Len=0 | |
| 21 | 0.040400 | 192.168.1.48 | 203.0.119.211 | TCP | 52028 → 80 [ACK] Seq=88 Ack=5833 Win=64240 Len=0 |
Seq and Ack are relative (as in Wireshark): they count from the initial number of each direction.