summaryrefslogtreecommitdiff
path: root/CHANGES
diff options
context:
space:
mode:
authorelie <elie>2013-05-05 11:11:51 +0000
committerelie <elie>2013-05-05 11:11:51 +0000
commita6bb3d327278d4a981b685aa01e02e053eb56115 (patch)
treeb58a163a6ceb237640da98f219128e81484442ca /CHANGES
parentb1031a19082078b845f21fa382cc52ee67806c12 (diff)
downloadpysnmp-a6bb3d327278d4a981b685aa01e02e053eb56115.tar.gz
Fix and significant logic rework of snmpCommunityTable to make it working
in both Generator and Responder modes and better follow RFC2576 requirements on sequential entries lookup and selection. As a side effect, untagged snmpCommunityTable entries will *not* match tagged snmpTargetAddrTable entries and vice versa.
Diffstat (limited to 'CHANGES')
-rw-r--r--CHANGES5
1 files changed, 5 insertions, 0 deletions
diff --git a/CHANGES b/CHANGES
index cd3bd4f..52f6bf7 100644
--- a/CHANGES
+++ b/CHANGES
@@ -24,6 +24,11 @@ Revision 4.2.5rc1
can't easily stop doing that.
- The snmpCommunityTable row selection improved to follow RFC2576, clause
5.2.1.
+- Fix and significant logic rework of snmpCommunityTable to make it working
+ in both Generator and Responder modes and better follow RFC2576
+ requirements on sequential entries lookup and selection. As a side effect,
+ untagged snmpCommunityTable entries will *not* match tagged
+ snmpTargetAddrTable entries and vice versa.
- Fix to Twisted-based NotificationOriginator to make it serving INFORMs again.
- Fix to rfc2576.v1tov2() logic: errorStatus = noSuchName is now translated
into rfc1905.noSuchObject exception value for *all* var-bindings. Although