agentx getnext handling

hi all,

a have a agentx subagent which register X.1 .. X.20 region.
and i have a `hole` ( only X.10 ... X.20 have values)

so if i use `snmpwalk X.1` to fetch a tree
client-agentx will trying to get reply:
get X.1
getNext X.1
getNext X.2
...
getNext X.10
now my handler replies with X.10 value
but in `handle_subagent_response` reply is filtered since (** scope
violation **)
and master-agentx going to repeat search starting from X.2
and agentx-client will iterate again up to X.10

can we avoid excessive looping in agentx-client ?
can we have a `hole` in registration region like a have ?

ps:
registration done via
netsnmp_handler_registration_create/netsnmp_register_handler
and range_subid/range_ubound specification.

net-snmp version - 5.3.2.2-5 from redhat.

------------------------------------------------------------------------------
OpenSolaris 2009.06 is a cutting edge operating system for enterprises 
looking to deploy the next generation of Solaris that includes the latest 
innovations from Sun and the OpenSource community. Download a copy and 
enjoy capabilities such as Networking, Storage and Virtualization. 
Go to: http://p.sf.net/sfu/opensolaris-get
_______________________________________________
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