Reading a tcpdump capture without guessing
Most “the network is slow” tickets end with a capture that nobody reads, because a raw pcap looks like noise. Two minutes of the right filters answer the question that matters: is the packet leaving, arriving, or being retransmitted?
Start with the direction, not the content
tcpdump -ni any -tttt 'host 203.0.113.10 and port 443' -c 400
Read the flags before the payload. A repeating [S] means the SYN is leaving but no SYN-ACK comes back — the path is filtered or the service is down. A repeating [P.] with the same sequence number means data is leaving and not being acknowledged — usually a broken return path, not a slow server.
Three filters that pay for themselves
'tcp[tcpflags] & tcp-syn != 0'— every new connection attempt, with timestamps. Shows whether clients even reach you.'tcp[tcpflags] & tcp-rst != 0'— who resets. A reset from your own host is a listen backlog or a firewall; from the middle, it is DPI or a load balancer.'greater 1200'— only large packets. Handy when small requests work and large responses hang.
Save once, analyse many times
Write to a file with a size limit, then read it with whatever tool you like. Rotating captures on a busy host are cheaper than re-creating the incident:
tcpdump -ni any -s 128 -w /var/tmp/edge-%H%M.pcap -G 600 -Z root 'port 443'
The -s 128 keeps headers and a little payload, which is enough for retransmission and handshake analysis and small enough to keep the disk alive.
What the capture cannot tell you
It cannot show a packet that never arrived. If you see SYNs leaving and nothing coming back, the next step is a capture on the other side, or a host outside the suspected path. Half a capture is a hypothesis; two captures are evidence.