On Thu, Jul 10, 2008 at 11:49:01AM +0400, [EMAIL PROTECTED] wrote: > Hi. I have two neigbour Tables in my MIB subtree. Second table goes right > after the first. Id of 1st is 3, and Id of 2nd is 4. > My problem is that after when i run snmpwalk for firstTable after > firstTable_handler() fucntion call there is a also call of > secondTable_handler() which mustn't.
Snmpwalk works by sending repeated GETNEXT requests to the agent and then it stops once it get a response that doesn't belong to the target tree. I guess that what you are seeing is the last GETNEXT that misses the end of the first table and returns the first entry of the second table. Given how SNMP works there is no real way to avoid this since this is generated by the client and not the agent. /MF ------------------------------------------------------------------------- Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! Studies have shown that voting for your favorite open source project, along with a healthy diet, reduces your potential for chronic lameness and boredom. Vote Now at http://www.sourceforge.net/community/cca08 _______________________________________________ Net-snmp-coders mailing list Net-snmp-coders@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
