I solve my problem by adding SIZE in the front of InetAddress when
displaying as index.

Thanks,

Fong
 

-----Original Message-----
From: Robert Story (Coders) [mailto:[EMAIL PROTECTED] 
Sent: Monday, November 15, 2004 3:35 PM
To: Fong Tsui
Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject: Re: Problem to display OID (Index out of range)

On Thu, 11 Nov 2004 14:59:21 -0800 Fong wrote:
FT> I found the problem but don't know where to fix it. 
FT> Since NetAddress is defined as OCTET (0, 255), in 
FT> _add_strings_to_oid(), it is treated as TYPE_OCTETSTR. So, the first

FT> OID of NetAddress is used as length of the string. That's why it is 
FT> error out with "Index out of range" if it is > 128.

If NetAddress does not define a fixed length, and the table index does
not use the IMPLIED keyword, then a length is required.

FT> Is there any patch fixing this? If not, Where should I look into to 
FT> fix that?

First we have to establish that the mib definition is valid and that
there is actually a bug.

--
Robert Story; NET-SNMP Junkie <http://www.net-snmp.org/>
<irc://irc.freenode.net/#net-snmp>
Archive:
<http://sourceforge.net/mailarchive/forum.php?forum=net-snmp-coders>

You are lost in a twisty maze of little standards, all different. 




-------------------------------------------------------
This SF.Net email is sponsored by: InterSystems CACHE
FREE OODBMS DOWNLOAD - A multidimensional database that combines
robust object and relational technologies, making it a perfect match
for Java, C++,COM, XML, ODBC and JDBC. www.intersystems.com/match8
_______________________________________________
Net-snmp-coders mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/net-snmp-coders

Reply via email to