2008/7/25 Jani Partanen <[EMAIL PROTECTED]>:
>> What is the result of the command
>>
>>    snmpgetnext -v2c -c `cat ~/.community` localhost ipv6TcpConnTable
>
>$ snmpgetnext -v2c -c `cat ~/.community` localhost ipv6TcpConnTable
> TCP-MIB::tcpConnectionState.ipv4."127.0.0.1".143.ipv4."195.12.58.115".35148
> = INTEGER: established(5)


That explains why things aren't working.

TCP-MIB::tcpConnectionState is part of the
(version-neutral) TCP-MIB::tcpConnectionTable
That's not the same as the v6-specific
IPV6-TCP-MIB::ipv6TcpConnTable, which is
what the snmpnetstat command is querying.

Long-term, the answer is probably for snmpnetstat
to be re-written to use the TCP-MIB table rather
than the two (older) version-specific tables.

Dave

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
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

Reply via email to