netdev - Re: What causes these TCP packet getting lost in linux kernel

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 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]

Date:	Sat, 12 Apr 2014 12:32:52 -0700
From:	Eric Dumazet <eric.dumazet@...il.com>
To:	Sharat Masetty <sharat04@...il.com>
Cc:	chptx y <chptxy@...il.com>,
	Linux Netdev List <netdev@...r.kernel.org>
Subject: Re: What causes these TCP packet getting lost in linux kernel

On Sat, 2014-04-12 at 12:35 -0600, Sharat Masetty wrote:
> Check /proc/net/netstat and /proc/net/snmp
> 
> In netstat look for
> 
> LINUX_MIB_TCPOFODROP and LINUX_MIB_BACKLOGDROP

The packet is not out of order, according to tcpdump.

Note that the receiver reacts to incoming packet, sending a DUPACK, so
its not a backlogdrop.

tcpdump trace is really incomplete, I asked tcpdump -vv but got nothing
from chptx, assuming this is a real name.

packet might be rejected because of a zero receiver window, who knows.

I might search in my basement this crystal ball I might have.

--
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