netdev - Re: 2.6.25: Weird IPv4 stack behaviour, IPv6 is fine

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 for Android: free password hash cracker in your pocket

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

Message-Id: <20080427.162620.221106869.davem@davemloft.net>
Date:	Sun, 27 Apr 2008 16:26:20 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	rmk@....linux.org.uk
Cc:	netdev@...r.kernel.org, xemul@...nvz.org
Subject: Re: 2.6.25: Weird IPv4 stack behaviour, IPv6 is fine

From: Russell King <rmk@....linux.org.uk>
Date: Mon, 28 Apr 2008 00:14:11 +0100

> Lastly, in /proc/net/snmp on lists, I find:
> 
> Ip: Forwarding DefaultTTL InReceives InHdrErrors InAddrErrors ForwDatagrams InUnknownProtos InDiscards InDelivers OutRequests OutDiscards OutNoRoutes ReasmTimeout ReasmReqds ReasmOKs ReasmFails FragOKs FragFails FragCreates
> Ip: 2 64 12771 0 0 0 0 0 5159 6262 9 0 2 8172 1363 2 922 0 5520
> 
> Note - InReceives = 12771, but InDelivers = 5159 - so roughly 50% of
> IPv4 packets were received but not delivered, which appears to tie up
> with the ping statistics.
> 
> Not sure what to make of this at the moment.  Any ideas?

The ReasmTimeout and ReasmFails look interesting.  Maybe it was the
namespace bits?

Pavel, could you take a quick look?

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