-
-
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
SetCMD error: timing parameters not in windows of trust #107
Comments
Interesting. Theoretically, this means that peer SNMP engine autodiscovery and time synchronisation procedure fails because either of SNMP parties does not keep up with the time. Could you please enable security-module debugging and attach its output to this issue?
Which pysnmp version are you using? May be try the latest released one? |
@etingof, tomorrow is a holiday in Brazil, so, after that I post the result here ok? thanks for replying so fast |
Hey, sure! Enjoy the holiday! ;-) |
Look, this Logger generates a lot of logs hahaha
|
What worries me in the log is that your SNMP agent does not return msgUserName in its second REPORT message:
This seems against RFC3414 section 3.2.2 which implies that msgUserName should be present. I wonder how Net-SNMP handles this though... What would be of great help to understand this business and possibly come up with some sort of compatibility mode for pysnmp is a tcpdump snoop of similar NEt-SNMP query. Even better if you would do both Net-SNMP and pysnmp queries within a single tcpdump session so I could peek at it and figure out the difference. ;-) |
I'm trying to set a var into an agent and i`m getting this error message "SNMP message timing parameters not in windows of trust" . But, when i'try using netsnmp it works
my python3 code is:
and the code above returns:
SNMP message timing parameters not in windows of trust
my netsnmp is below:
returns
SNMPv2-MIB::sysName.0 = STRING: new system name python
What i`m doing wrong? anyone can help me?
The text was updated successfully, but these errors were encountered: