>>>>> On Thu, 13 Jan 2011 16:57:19 +0100, Jacek Poplawski >>>>> <[email protected]> said:
JP> TCP-MIB::tcpConnectionState.ipv4.\"192.168.85.92\".56470.ipv4.\"192.168.85.53\".22 JP> Error in packet JP> Reason: (noSuchName) There is no such variable name in this MIB. JP> Failed object: TCP-MIB::tcpConnectionState.ipv4."192.168.85.92".56470.ipv4."192.168.85.53".22 JP> Could you explain should "4" (between "1" and IP) be in the OID or JP> not? Yes. It gives the length of address following it so that it can be properly decoded. Although you could determine the length from the IP address type, the OID encoding rules state that the string that makes up the actual address needs a '4' in front of it as well. -- Wes Hardaker Please mail all replies to [email protected] ------------------------------------------------------------------------------ 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
