Fix SNMP v1/v2c regression in async libraries #2763
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The
SNMPParameters
class expects its SNMP version attribute to be an integer. However, some (or perhaps all) SNMPv1/v2c management profiles tend to store the version numbers as strings, for some reason.The net result is that the
as_agentproxy_args()
method would fail to provide acommunity
argument to SNMP v1/v2 sessions because it was unable to compare an integer version number to a string. This would causeipdevpoll
/navoidverify
/naventity
to always usepublic
as the SNMP community of all v1/v2c sessions.Fortunately, this did not make it into a release.