[SNMP4J] Wrong SNMP Enterprise parsed from trap by SNMP4j

[Frank Fock]

Hi Soumya,

You can send the hexdump of the trap PDU to support at snmp4j.org.
There is no known issue. Some devices/agents implement a wrong length
encoding of BER elements, but its not clear what could have caused
that issue from the facts your provided.

Best regards,
Frank

Am 22.01.2014 10:20, schrieb Chatterjee, Soumya Subhra:
> Hi all/Frank
>
> Recently I came across traps (v1) by Appsmon application. Capturing the packet using Wireshark and examining its properties gives an Enterprise OID of 2.2205.122.39 but when SNMP4j parses the trap the same comes out as 57.5.122.39
>
> Why are the values coming out to be different? Is there any known issue about it?
>
> If you want to take a look at it, I can provide code snippets, wireshark capture of the trap, and screenshots, if you can give a location/email id where I can provide that.
>
> Soumya Subhra Chatterjee
> CA Technologies
> Associate Software Engineer
> Tel:  +914066877206
> SoumyaSubhra.Chatterjee at ca.com
>
> _______________________________________________
> SNMP4J mailing list
> SNMP4J at agentpp.org
> https://s16675406.onlinehome-server.info/mailman/listinfo/snmp4j

-- 
---
AGENT++
Maximilian-Kolbe-Str. 10
73257 Koengen, Germany
https://agentpp.com
Phone: +49 7024 8688230
Fax:   +49 7024 8688231