netdev - Re: Detecting TCP loss on the receiving side?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <48767BAA.3090704@hp.com>
Date:	Thu, 10 Jul 2008 14:14:18 -0700
From:	Rick Jones <rick.jones2@...com>
To:	Dan Noé <dnoe@...ebrokerage.com>
CC:	netdev@...r.kernel.org
Subject: Re: Detecting TCP loss on the receiving side?

Dan Noé wrote:
> Rick Jones wrote:
> 
>> If this is just for troubleshooting, why not just take a tcpdump trace?
> 
> 
> We're pushing a lot of data.. several Mbps pretty much all day long.. 
> and the (suspected) loss occurs sporadically.  Ideally we'd like to be 
> able to easily correlate it with latency seen in our app.

If your app can already log a timestamped "high latency" warning, then 
it would simply be a matter of a big disc and comparing timestamps in 
the tcpdump trace :)

Also, it appears that for what you want, you only need to capture up 
through the TCP header, so while it may be many Mbit/s on the wire, it 
will be fewer Mbit/s in the trace.

rick jones
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html