I think I see what my problem is and how to, perhaps, fix it. Just to make sure that I understand things correctly - after all I am fairly new to this, so please bear with me.
The Way It Should Work (tm): The IP-FORWARDING-MIB.txt that comes with net-snmp 5.2.1 was used by mib2c to compile the skeleton code ip-forwarding-mib Implementation, part of which is the inetCidrRouteTable. The tools use the same IP-FORWARDING-MIB.txt to represent "the bucket of bits" recieved from the Agent. Because the same MIB was used when building the Agent and the Tools, everybody is happy. The Way It it may be Broken: The IP-FORWARDING-MIB that comes with netsnmp 5.2.1 is outdated, but due to an unfortunate accident, the latest IP-FORWARDING-MIB was used by mib2c to generate the ip-forwarding-mib implementation. Thus the Agent is correct, but the Tools are confused. This is beneign as getting the latest IP-FORWARDING-MIB will resolve the tools confusion making us all Happy. The IP-FORWARDING-MIB that comes with netsnmp 5.2.1 *is* the latest, but the one used to generate the ip-forwarding-mib implementation is an obsolete one. Again, the agent will fetch proper information but it will drop it into obsolete/wrong OID's and there may be bits missing because OID's might have been added during the development of the IP-FORWARDING-MIB This is Not So Good - because I will have to run mib2c on the latest IP-FORWARDING-MIB and compare the result with the ip-forwarding-mib implementation and see what is broken/missing. (Probably not very much, but Work). That is my understanding so far, is that reasonable? >> - I think the root cause is that the build is broken somehow?? >No - it's just that you're working with the cutting edge of SNMP >routing management, and you need to install the relevant MIBs >yourself. There's nothing wrong with the build. One Nit and a Rant :) If the MIB's supplied and the Source do not Match each other; weell, That's Broken. Like headers not matching the code (in c or c++). *Anything* involving IPv6, that are not entirely trivial "user-side" applications on a host (with *one* interface), is Bleeding Edge!!! As soon as one starts to build a network that is *entirely IPv6* and just happen to need the same "Infrastructure" as available Now with IPv4; Problems, Untested Application Dependencies, More Bugs, Missing Tools and Incompatibilities between tools forced together by the IPv6 requirement creep up on you!!!! One should not think so, IPv6 being long standardized and all, but that is Our experience. ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_ide95&alloc_id396&op=click _______________________________________________ Net-snmp-coders mailing list Net-snmp-coders@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
