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

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

Message-ID: <467F50E3.2050405@linux.vnet.ibm.com>
Date:	Mon, 25 Jun 2007 10:51:39 +0530
From:	Varun Chandramohan <varunc@...ux.vnet.ibm.com>
To:	YOSHIFUJI Hideaki / 吉藤英明 
	<yoshfuji@...ux-ipv6.org>
CC:	netdev@...r.kernel.org, sri@...ibm.com, dlstevens@...ibm.com,
	varuncha@...ibm.com
Subject: Re: [PATCH] Age Entry For IPv4 Route Table

YOSHIFUJI Hideaki / 吉藤英明 wrote:
> In article <20070625102838.9d1fee20.varunc@...ux.vnet.ibm.com> (at Mon, 25 Jun 2007 10:28:38 +0530), Varun Chandramohan <varunc@...ux.vnet.ibm.com> says:
>
>   
>> 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.
>>     
>
> I'm not in favor of adding new field(s) to /proc/net/route.
>
>   
Do you think it will break any user level functionality? I have tested
with netstat, route and net-snmp which reads from the same /proc
interface. They seem to work fine.
> --yoshfuji
> -
> 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
>   

-
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