-
Notifications
You must be signed in to change notification settings - Fork 339
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
Only one of the two correct connection parameters can be correctly connected. #395
Comments
I find that only when PrivacyProtocol is AES-256 or AES-192 the error has occurred |
Hi @haodayitiaoyu666. Can you share what version of gosnmp you are on and, if possible, some code to reproduce the issue? |
v1.34.0 has this problem. |
Thank you. That doesn't seem right indeed. Will have a look at it. |
We have two correct SNMPv3 protocol parameters A and B.
Invoke the snmp.Get interface.
Use the A to connect first,the correct result is obtained. Then use the B to connect second,the result is:
result &{Version:3 MsgFlags:1 SecurityModel:3 PDUType:168 RequestID:0 Error:NoError ErrorIndex:0 NonRepeaters:0 MaxRepetitions:0 Variables:[{Name:.1.3.6.1.6.3.15.1.1.6.0 Type:Counter32 Value:12}] SnmpTrap:{Variables:[] IsInform:false Enterprise: AgentAddress: GenericTrap:0 SpecificTrap:0 Timestamp:0}}
Use the B to connect first,the correct result is obtained. Then use the A to connect second,the result is the same
this is snmpV3 parameter
Below is the tcp dump. Any ideas why this might be happening?
The text was updated successfully, but these errors were encountered: