; used. The default would be full conformance. Enabling the configuration
> item would allow this non-conforming condition, using if statements on the
> configuration item in the code above for looking ahead.
>
> Thank you,
> Jerome
>
>
> ____
> From: snmp4j-
in the code above for looking ahead.
Thank you,
Jerome
From: snmp4j-boun...@agentpp.org [snmp4j-boun...@agentpp.org] on behalf of
Frank Fock [f...@agentpp.com]
Sent: Monday, November 26, 2012 5:12 PM
To: snmp4j@agentpp.org
Subject: Re: [SNMP4J] v2 PDU in v1 message
Hello Jerome
Hello Jerome,
I will not add code to SNMP4J that violates the SNMP standards.
If you need such code, you are free to change it in your version.
Nevertheless, if some hook methods would help you to
clarly separate your code from the SNMP4J code, I am willing
to add such hook methods.
Best regards,
Hello,
We have some devices which send traps in a v2 PDU but in a v1 message. snmp4j
discards these. I've come up with a source code change which looks ahead in v1
message processing to see if it's a v2 PDU and creates a v2 PDU instead of a v1
PDU if so. I've tested and it's working well.
