Il 06/06/2011 06:47 PM, Robert Story ha scritto:
> On Tue, 31 May 2011 12:07:48 +0200 Leo wrote:
> LC> If I understand correctly the documentation and the code, with this
> LC> approach I would have to write routines for encoding/decoding the
> LC> application data types into a buffer accordingly t
> On Thu, 2 Jun 2011 16:47:02 +0530, Nilesh karle
> said:
Nk> I found the issue in "mteTrigger.c" .
Nk> The snmpd is not able to query the "mteTriggerValueID" [ObjID]. The function
Nk> "netsnmp_query_get" returns with "SNMP_ERR_NOSUCHNAME".
Nk> When I query the same OID through snmpget
Robert Story wrote:
> sorry for the delay, I took a little vacation.
Hmmm, I don't remember +3 votes for any vacation - did I miss something?
:-)
--
Simplify data backup and recovery for your virtual environment with vR
On Tue, 31 May 2011 12:07:48 +0200 Leo wrote:
LC> If I understand correctly the documentation and the code, with this
LC> approach I would have to write routines for encoding/decoding the
LC> application data types into a buffer accordingly to some ASN.1 encoding
LC> scheme (presumably BER or CER).
sorry for the delay, I took a little vacation.
On Tue, 17 May 2011 17:15:54 +0200 Giuseppe wrote:
GM> Now I understand. The handler should returns always
GM> SNMP_ERR_NOERROR, but the variable should be marked with an error
GM> code with netsnmp_set_request_error().
Exactly.
GM> Thank you for
On 6 June 2011 10:02, Leo Cacciari wrote:
> Should the code be under a defined(NETSNMP_WITH_OPAQUE_SPECIAL_TYPES)
> switch?
No, I don't think so.
That flag is really intended for special Opaque-based types
that the library recognises (and can handle internally).
(Such as the Float/Double types, o
Il 06/06/2011 10:45 AM, Dave Shield ha scritto:
>[...snip...]
>> What I'm thinking is adding a 'X' type flag meaning something
>> like "the data is to be sent as 'opaque' and here it follows the data
>> itself ber-encoded and written as an hex string."
>
> Yes - that seems a perfectly sensible e
On 5 June 2011 13:26, Leo Cacciari wrote:
> AFAIK, there is no way for
> the user of snmpset to specify a type of opaque
That's correct.
In general, use of Opaque-based types works best
when they are handled within the library (as is done
with the Float/Double special types). Providing
direct
