netdev - Re: [PATCH] Age Entry For IPv4 Route Table

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

Message-Id: <20070625161014.180cb972.dada1@cosmosbay.com>
Date:	Mon, 25 Jun 2007 16:10:14 +0200
From:	Eric Dumazet <dada1@...mosbay.com>
To:	Varun Chandramohan <varunc@...ux.vnet.ibm.com>
Cc:	netdev@...r.kernel.org, sri@...ibm.com, dlstevens@...ibm.com,
	varuncha@...ibm.com
Subject: Re: [PATCH] Age Entry For IPv4 Route Table

On Mon, 25 Jun 2007 10:28:38 +0530
Varun Chandramohan <varunc@...ux.vnet.ibm.com> wrote:

> According to the RFC 4292 (IP Forwarding Table MIB) there is a need for an age entry for all the routes in the routing table. The entry in the RFC is inetCidrRouteAge and oid is inetCidrRouteAge.1.10.
> Many snmp application require this age entry. So iam adding the age field in the routing table and providing
> the interface for this value via /proc/net/route.
> 

Hi Varun

If you find a way to expose this information without breaking /proc/net/route, please consider that jiffies can wrap
every 49 days on 32 bit platforms.
So you probably want to use an other time infrastructure if you want meaningfull Age information.
-
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