Menu

A small ACK can hide a failed return path: collecting both endpoint logs
📰

A small ACK can hide a failed return path: collecting both endpoint logs

DEV Community: python·Doğukan Sağlık·7 days ago
#jbtGp2K0
#devtopython#devto#dev#receiver#json
Reading 0:00
15s threshold

When a tunnel or routed path passes ping but stalls on bulk transfers, testing large UDP payloads in one direction is only half the story. If a receiver answers a 1400-byte probe with a 24-byte acknowledgement, an acknowledged result only records that 1400 bytes arrived forward and 24 bytes made it back. When the return path has a narrower MTU, small ACKs can succeed while large return payloads fail.

I maintain TunnelScope , an alpha Python CLI that combines bounded UDP probes, --sized-reply , and offline endpoint log correlation. With --sized-reply enabled on both sides, a Linux (including WSL2) or Windows receiver attempts a reply of the probe's own payload size. Joining both logs records receiver arrival, the receiver socket's send outcome, and whether the sender received that reply. A missing receiver entry is inconclusive without verified capture coverage; a successful socket send alone does not locate a later failure.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.