rfc 2741 compliance

hi!

i have a question regarding RFC 2741 "7.2.3.2. Subagent Processing of
the agentx-GetNext-PDU"

i use snmpwalk to walk over my mib, snmp dump:

( name is netsnmp_variable_list->name value, and range is
netsnmp_request_info->range_end )

mode: 160
inclusive: 1
range: xxx.1.2.1.15527.
name: xxx.1.2.1.15526.
-> reply with value xxx.1.2.1.15526

mode: 161
inclusive: 0
range: xxx.1.2.1.15527.
name: xxx.1.2.1.15526.
-> reply with end-of-mib

mode: 161
inclusive: 1
range: xxx.1.2.2.15527.
name: xxx.1.2.1.15526.

and...
i have 2 variables: xxx.1.2.1.15526 and xxx.1.2.2.15526
according to RFC i must return xxx.1.2.1.15526 ( since inclusive flag is set)
but if a make this - then snmpwalk reports that "Error: OID not increasing"

if i ignoring RFC and return xxx.1.2.2.15526 - all is ok.

is net-snmp really not rfc-compliant in this part or i miss something?

------------------------------------------------------------------------------
The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
production scanning environment may not be a perfect world - but thanks to
Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700
Series Scanner you'll get full speed at 300 dpi even with all image 
processing features enabled. http://p.sf.net/sfu/kodak-com
_______________________________________________
Net-snmp-users mailing list
[email protected]
Please see the following page to unsubscribe or change other options:
https://lists.sourceforge.net/lists/listinfo/net-snmp-users