On Mon, 25 Jun 2007 10:28:38 +0530
Varun Chandramohan <[EMAIL PROTECTED]> 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 s
From: Varun Chandramohan <[EMAIL PROTECTED]>
Date: Mon, 25 Jun 2007 13:28:37 +0530
> Ok i understand. But can you suggest anyother way to do the above?
Just because I found a fault in your patch doesn't mean that
it becomes my job isn't to implement the feature for you.
-
To unsubscribe from this
David Miller wrote:
> From: Varun Chandramohan <[EMAIL PROTECTED]>
> Date: Mon, 25 Jun 2007 10:51:39 +0530
>
>
>> YOSHIFUJI Hideaki / wrote:
>>
>>> In article <[EMAIL PROTECTED]> (at Mon, 25 Jun 2007 10:28:38 +0530), Varun
>>> Chandramohan <[EMAIL PROTECTED]> says:
>>>
>>>
YOSHIFUJI Hideaki / 吉藤英明 wrote:
> In article <[EMAIL PROTECTED]> (at Mon, 25 Jun 2007 10:28:38 +0530), Varun
> Chandramohan <[EMAIL PROTECTED]> 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 entr
In article <[EMAIL PROTECTED]> (at Mon, 25 Jun 2007 10:28:38 +0530), Varun
Chandramohan <[EMAIL PROTECTED]> 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