On 21 July 2010 14:22, Gaurav Chaturvedi <[email protected]> wrote:
> The actual value contains the characters I cannot type using keyboard and
> even can't copy (like 5 squares). So, it is very difficult to provide you
> the same.
The engine ID is a binary string, so I wouldn't expect it to be printable.
But you should be able to print the individual byte values
i.e. secEngineID[0], secEngineID[1], etc
If you print these as decimal or hex values, that would give the information
we need.
Also, if you include the following code in your trap receiver:
netsnmp_ds_set_boolean(NETSNMP_DS_LIBRARY_ID,
NETSNMP_DS_LIB_DUMP_PACKET, 1);
this would display the raw packets as are received.
This might also give some indication as to what is happening.
> Can you also tell me the procedure to implement/contribute enhancements in
> net-snmp code.
If you go to the project web site (www.net-snmp.org), under the heading
"Support" there are links to the Bug and Patches trackers. These can
be used to log problem reports and enhancements.
Dave
------------------------------------------------------------------------------
This SF.net email is sponsored by Sprint
What will you do first with EVO, the first 4G phone?
Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
_______________________________________________
Net-snmp-users mailing list
[email protected]
Please see the following page to unsubscribe or change other options:
https://lists.sourceforge.net/lists/listinfo/net-snmp-users
