linux-kernel - ipReasmTimeout in /proc/net/snmp is wrong

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>] [day] [month] [year] [list]

Message-Id: <200907271939.n6RJdjtk031717@dell2.home>
Date:	Mon, 27 Jul 2009 19:39:45 +0000
From:	"Marty Leisner" <leisner@...hester.rr.com>
To:	linux-kernel@...r.kernel.org
cc:	martyleisner@...oo.com
Subject: ipReasmTimeout in /proc/net/snmp is wrong

In RFC1213/2011, it says:

ipReasmTimeout OBJECT-TYPE
    SYNTAX      Integer32
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
            "The maximum number of seconds which received fragments are
            held while they are awaiting reassembly at this entity."
    ::= { ip 13 }

This is correctly reflected in
/proc/sys/net/ipv4/ipfrag_time

>From /proc/net/snmp:
IP:ReasmTimeout is a counter -- incremented in net/ipv4/ip_fragment/ip_expire.

I think this is incorrect.
(this is in all kernels from 2.6.20-30).

Note sure what will be the most expedient way to rectify this.


marty
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/