#26 Bad interpreting of integer value

v1.0_(example)
open
nobody
5
2014-07-04
2014-07-04
Master SUK
No

Hi!

I'm implementing an SNMP agent and testing it against some SNMP managers. While using SnmpB, I've found maybe an error while interpreting one value. Other managers (NET-SNMP, iReasoning MIB Browser) interprets this value correctly, so I think the problem is in SnmpB. The correct value is Integer(2), but SnmpB displays 2293700, which is obviously wrong.

I'm attaching capture (with "udp port 161" filter) from wireshark containing only Request and Response. This error is unlimitedly reproducible, but fails only on this one value (other integer values containing number 2 works OK).

1 Attachments

Discussion