Thanks for response, but I found the problem and fix it.
The problem was in the "_get_first_data_point" (and "_get_next_data_point")
functions. For function "snmp_set_var_value", prevoiusly I use a string
variable (all project is written in the C++) to setting index which is
ASN_IPADDRESS type (use 4 bytes for it; length of this string is 4):
snmp_set_var_value(vptr, (u_char *)tIndex->m_multicastGroupIpAddress.c_str(),
tIndex->m_multicastGroupIpAddress.length());
Now I change it, and use "u_long" type variable, for setting these indexes.
Dejan
________________________________
From: Dave Shield <d.t.shi...@liverpool.ac.uk>
To: Dejan Bojic <b.de...@ymail.com>
Cc: net-snmp-users@lists.sourceforge.net
Sent: Mon, November 30, 2009 12:08:04 PM
Subject: Re: IPAddress like index for MIB table
2009/11/25 Dejan Bojic <b.de...@ymail.com>:
> a GET request will return: radiusServerCurrentMode.192.168.1.20
> a GET_NEXT request will return: radiusServerCurrentMode.20.1.168.192
> Is anybody has any idea why I got index in the opposite order?
This sounds like a bug in the code that implements this MIB.
What does this code look like?
Dave
------------------------------------------------------------------------------
Join us December 9, 2009 for the Red Hat Virtual Experience,
a free event focused on virtualization and cloud computing.
Attend in-depth sessions from your desk. Your couch. Anywhere.
http://p.sf.net/sfu/redhat-sfdev2dev
_______________________________________________
Net-snmp-users mailing list
Net-snmp-users@lists.sourceforge.net
Please see the following page to unsubscribe or change other options:
https://lists.sourceforge.net/lists/listinfo/net-snmp-users
