I am running snmpd on a Turris Omnia. From a nearby monitoring system, I can retrieve ipRouteTable but not ipv6RouteTable, as shown below.
Is there something I can configure to expose the IPv6 routes?
dash(maint)$ snmpwalk -mALL -v2c -On -cpublic turris.local ipRouteTable | wc
40 160 2107
dash(maint)$ snmpwalk -mALL -v2c -On -cpublic turris.local ipv6RouteTable
.1.3.6.1.2.1.55.1.11 = No Such Object available on this agent at this OID
dash(maint)$
The command you suggest shows what I expect. It is worth asking me to confirm that the IPv6 routing table isn’t just empty, but I’m not sure that disclosing my IPv6 routing table is relevant to what appears to be missing support for IPv6 in snmpd.
FWIW, here is a demonstration that my IPv6 routing table isn’t empty:
niall@m2a ~ % ssh turris.local ip -6 route show | wc
31 178 1370
niall@m2a ~ %
Of course, I could write a helper script around ip -6 route show, and have snmpd serve the subset I want of the IPv6 routing table from helper-script OID space instead of from ipv6RouteTable. I may end up doing that if support for ipv6RouteTable in snmpd is not expected any time soon.