Integer value parsed incorrectly in some cases about node-net-snmp HOT 5 CLOSED

Hi Sergey,

Sorry for the delay in my response.

This would suggest an issue with the structure of the response packet.

Are you able to send me a Wireshark capture which includes the SNMP response packet (or similar)?

Thanks

Steve

from node-net-snmp.

Hi Stephen!
No worries, my fork with a hack that checks for the 129 value surprisingly works for all of the devices I have at hand :)
I guess there may be wrong structure in the response, and I never would create and issue here but for snpmget getting a good result.
I'll create a capture ASAP, wen I get my hands on the device again.

from node-net-snmp.

That's ok, I understand.

If there is an issue there I would like to address it for you.

Thanks

Steve

from node-net-snmp.

If you would like to look into this further just reopen the issue and I will continue to investigate.

Thanks

Steve

from node-net-snmp.

This is long closed, but @burmisov if you're still out there, and you still care, this issue is fixed in version 2.9.8 of the npm. See #136 for further details of the problem and fix.

from node-net-snmp.