There was no reply to my issue for 7 days so I will try to explain it once again. Please repeat these steps yourself if you think I am wrong. And if I am wrong please explain at which point I am doing mistake.
I use Net-SNMP as a reference. I started snmpd and I use snmpwalk/snmpget to communicate with it. I use MIBs from Net-SNMP too. For this example I created ssh connection from host 192.168.85.92 to host 192.168.85.53. I am able to walk tcpConnectionTable as you can see: [jacek@myhost ~]$ snmpwalk -v 1 -c public localhost TCP-MIB::tcpConnectionState|grep 53 TCP-MIB::tcpConnectionState.ipv4."192.168.85.92".52219.ipv4."192.168.85.53".22 = INTEGER: established(5) I am NOT able to reach this object by giving full OID: [jacek@myhost ~]$ snmpget -v 1 -c public localhost TCP-MIB::tcpConnectionState.ipv4.\"192.168.85.92\".52219.ipv4.\"192.168.85.53\".22 Error in packet Reason: (noSuchName) There is no such variable name in this MIB. Failed object: TCP-MIB::tcpConnectionState.ipv4."192.168.85.92".52219.ipv4."192.168.85.53".22 I am also NOT able to walk this objects when I put at least half of instance identifier in OID: [jacek@myhost ~]$ snmpwalk -v 1 -c public localhost TCP-MIB::tcpConnectionState.ipv4.\"192.168.85.92\" [jacek@myhost ~]$ But I am able to walk it when I use just "ipv4" part: [jacek@myhost ~]$ snmpwalk -v 1 -c public localhost TCP-MIB::tcpConnectionState.ipv4 |grep 53 TCP-MIB::tcpConnectionState.ipv4."192.168.85.92".52219.ipv4."192.168.85.53".22 = INTEGER: established(5) This was issue description, but I have also suspect what's wrong. This is OID in raw format: [jacek@myhost ~]$ snmpwalk -O n -v 1 -c public localhost TCP-MIB::tcpConnectionState|grep 53 .1.3.6.1.2.1.6.19.1.7.1.4.192.168.85.92.52219.1.4.192.168.85.53.22 = INTEGER: established(5) And this is snmpget with this OID: [jacek@myhost ~]$ snmpget -O n -v 1 -c public localhost 1.3.6.1.2.1.6.19.1.7.1.4.192.168.85.92.52219.1.4.192.168.85.53.22 .1.3.6.1.2.1.6.19.1.7.1.4.192.168.85.92.52219.1.4.192.168.85.53.22 = INTEGER: established(5) I found that Net-SNMP doesn't include "4" in the OID, that's why when giving raw OID it works and when giving text name it doesn't. I found it when implementing support for IPv6 in my application and used Net-SNMP and SilverCreek to test it. That's why I asked about this "4" in OID, because I am not able to find clear description of size of InetAddress after InetAddressType. Could you point me to any RFC about it? I know RFC 4001 but maybe I don't understand correctly where is the information when to put size in OID. (the last paragraph is not related to bug report at all). ------------------------------------------------------------------------------ Protect Your Site and Customers from Malware Attacks Learn about various malware tactics and how to avoid them. Understand malware threats, the impact they can have on your business, and how you can protect your company and customers by using code signing. http://p.sf.net/sfu/oracle-sfdevnl _______________________________________________ Net-snmp-coders mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
