> Try the inetCidrRouteTable instead. As in --with-mib-modules=" ... ip-forwarding-mib/inetCidrRouteTable ... "?
Hmm - There is one thing, though: Does the creation of the *Route* tables in any way depend on the status of the "ipForwarding" flag? PS: This may be caused by my application of SNMP: The nodes are Ad-Hoc nodes, which are conceptually Routers but making them Routers (in the IETF-RFC-Compliant sense) will break stuff one *needs & wants* such as IPv6 Multicast and Neighbour Discovery. Hence the "Router Process", f.ex. AODV, uses the "ip route" and "Netlink" tools update the forwarding table when they discover topology changes. Basically, to track this without too much work, I need to see the forwarding table via SNMP like I can locally via "ip route" to do what everybody else does: Build a list of nodes on the network with some topology information (we do not care for switches f.ex.) in order to avoid polling "everything" which will take a looong time on a sparsely-populated IPv6 subnet and use that "list" to build a configuration for my Management System (yes - nodes can also move to other networks/subnets). ------------------------------------------------------- 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 [email protected] https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
