Get the latest tech news
Debugging the little SSH that sometimes couldn't
a blog post by @azwinkau
Happy that we were no longer suffering from this problem and that our systems are caught up with the backlog, I decided I’d try my hand at actually finding the device causing the corruption. A TCP peer that acts as an echo server to mirror back the data it received, so we get inspect it at the sending node and detect corruption there It was the first in Y hops of upstream2 – right at the edge between upstream1 and upstream2, corrupting random TCP packets, causing many retries, and, depending on the protocol’s logical back-and-forth, hangs, or reduced transmission rates.
Or read this on Hacker News