Q 1. I was wondering if there is a reason why for both IPv4 and IPv6 we need to
use a full hex string to set
snmpTargetAddrTAddress for a net-snmp agent?
e.g.
snmpset <security details> <ip address> snmpTargetAddrTAddress.\'name1\' x
0x0a0a0a6400a2
snmpset <security details> <ip address> snmpTargetAddrTAddress.\'name2\' x
0xfe80000000000000021e2afffeb37eaca200
as opposed to "10.10.10.10:162", "fe80::21e:2aff:feb3:7eac", "[fd80::1:]" etc
which would be quite useful.
Is this simply following the textual conventions for TransportAddressIPv4 and
TransportAddressIPv6?
Q 2. As an aside, netsnmp_udp_create_ostring() does a htons() on the port
number whereas
netsnmp_udp6_create_ostring() doesn't. Is this just an oversight or is there a
reason?
Q 3. netsnmp_udp6_create_ostring() does not allow for provisioning
addr.sin6_scope_id whereas when the
master agent session is created via:
init_master_agent()
netsnmp_transport_open_server()
netsnmp_tdomain_transport_full()
netsnmp_udp6_create_tstring()
scope_id is set. Is this deliberate? Does it fall under transportDomainUdpIpv6z
transport type?
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
