There seems to be an issue in parsing value-range constraints. Consider the following toy MIB:
MY-MIB DEFINITIONS ::= BEGIN
IMPORTS OBJECT-TYPE, Integer32 FROM SNMPv2-SMI;
my-parameter OBJECT-TYPE
SYNTAX Integer32 (100..200)
MAX-ACCESS read-only
STATUS current
DESCRIPTION "Simple parameter"
::= { iso 1 }
END
The exitValueConstraint method process the constraints and eventually creates an ValueRangeConstraint instance with lowerbound of 200 and no upperbound. There is possibly an issue inside for loop in determining the presence of low and upper bounds.
There seems to be an issue in parsing value-range constraints. Consider the following toy MIB:
The exitValueConstraint method process the constraints and eventually creates an
ValueRangeConstraintinstance with lowerbound of 200 and no upperbound. There is possibly an issue insideforloop in determining the presence of low and upper bounds.