>
> So, the value of { 0 0 } is appropriate, and NOT A BUG.
> The NETSNMP code MUST NOT be changed to return another value!
Don't worry, David. I have no intention of doing so.
It's one of the few areas of this agent that I'm 100% confident about :-)
Dave
-
HI,
Again. DO NOT ADD CODE FOR ifSpecific.
For what purpose do you plan on using it?
At 10:20 PM 8/24/2004 +0530, Karthikeyan N wrote:
>Hi Dave,
>
>Did u mean to say that, we need to implement the ifSpecific with right OID's for each
>interfaces?
>
>If so, where do we get those object identifie
HI,
Please note. You should not use ifSpecific because it really
doesn't provide you with any useful info. This is a long known
problem, and is described in section 3.1.16 of RFC 2863.
So, the value of { 0 0 } is appropriate, and NOT A BUG.
The NETSNMP code MUST NOT be changed to return another v
actly available?
Thanks for your help.
Regards,
Karthik. N
- Original Message -
From: Dave Shield <[EMAIL PROTECTED]>
Date: Tue, 24 Aug 2004 14:56:08 +0100
To: "Karthikeyan N" <[EMAIL PROTECTED]>
Subject: Re: ifSpecific attribute
>
> > I am trying to w
> I am trying to walk the column ifSpecific in ifTable,
> Apart from 0.0 in the result, can we get some other response?
No.
Not without hacking the code.
Dave
---
SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media
100pk S
