2009/2/24 Alexander Bubnov <[email protected]>: > Sending 50 bytes to UDP: [0.0.0.0]->[127.0.0.1]:161 : > 0032: ... 06 0D 2B 06 01 04 01 BF 08 02 04 01 01 02 00
That's the OID which you are asking for... > 0048: 05 00 followed by a NULL value > Received 66 bytes from UDP: [0.0.0.0]->[127.0.0.1]:161 > 0032: .. 06 0D 2B 06 01 04 01 BF 08 02 04 01 01 02 00 There's the same OID again. > 0048: 04 10 Followed by a string value (16 octets) > 44 00 00 00 45 00 00 00 46 00 00 00 00 00 ..D...E...F..... > 0064: 00 00 .. containing the DEF string, followed by a '\0' trailing wide-character. > NET-SNMP-TUTORIAL-MIB::nstAgentSubagentObject.0 = STRING: D So yes - it's the output routines that are going wrong. So now we just need a volunteer to look at the library output code and suggest how best to fix it. Dave ------------------------------------------------------------------------------ Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise -Strategies to boost innovation and cut costs with open source participation -Receive a $600 discount off the registration fee with the source code: SFAD http://p.sf.net/sfu/XcvMzF8H _______________________________________________ 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
