I think parts of my last message were cut off. I'll try again. We are in the process of updating our agent/MIB to support both IPv4 and IPv6 addresses. As well as the agent itself, our proprietary MIB specifies a number of external IP addresses e.g. the address of a syslog client. Looking at the ways to specify addresses, there seems to be the approach used in the SnmpTargetAddrEntry table combining address and port:
snmpTargetAddrTDomain = snmpUDPDomain, transportDomainUdpIpv6, etc. [Strange that this now a mix of snmpDomains and transportDomains. Any reason for this?] snmpTargetAddrTAddress = "1.2.3.4/161", etc or: making use of the InetAddress address syntax. InetAddressType ipv4(1), ipv6(2), ipv4z(3), ipv6z(4), dns(16) InetAddress "1.2.3.4", "2x:2x:2x:2x:2x:2x:2x:2x" etc. Is it correct to assume that InetAddress is a direct replacement for (the old IPv4) IpAddress and the convention dictates that it always needs to be accompanied by InetAddressType? Similarly have there been any standard conventions adopted for updating MIBs to support both Ipv4 and IPv6 e.g. keep the same name for the attribute but change the syntax or add a new attribute and continue to support old attribute if address is IPv4? Any suggestions appreciated. Regards, Adam. ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Net-snmp-coders mailing list Net-snmp-coders@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
