-
-
Notifications
You must be signed in to change notification settings - Fork 203
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SNMPv3 inform: No SNMP response received before timeout #290
Comments
Sorry , if it is a wrong place to post my queries. |
That's a perfectly good place to raise such issues! What looks suspicious to me is:
in the very last packet. It appears like notification originator resets those counters abruptly. There has been a potentially relevant fix in pysnmp 4.4.10, could you please retry your test with it? We will look deeper if that does not solve it. Thank you for the quality report! |
Thanks for your reply, I will get back to you with 4.4.10 results. |
It's still the same case, Engineboot and time is getting reset to 0 with pysnmp==4.4.10 below is log snippet
Below is the notification senderlogs
|
SHA authentication was broken by a mistake in code https://github.com/etingof/pysnmp/blob/v4.4.9/pysnmp/proto/secmod/rfc3414/localkey.py#L67 #398 was aiming to fix it, but only integrated by the forks (such as |
we are building a SNVPv3 inform collector , and am trying to create a snmp-v3 agent stub for unit-testing the collector.
I am failing to get snmp ack for the Inform and notification generator timesout. Can you please help me with example code/pointing errors in my code. Thanks.
pysnmp==4.4.9
On the receiver side I get below logs:
##below is the code snippet
#Notification receiver:
#Notification Sender:
Below are the wired packets:
Discovery Packet:
#Inform
The text was updated successfully, but these errors were encountered: