Hi Dave, Okay, I re-compiled with IPv6 enabled for the remote machine. Now it appears sometimes query with IPv6 address worked, but other times it returned "No Response". Ping6 always succeeded though.
$ /bin/ping6 fe80::200:50ff:fe3d:7aac -I eth1 PING fe80::200:50ff:fe3d:7aac(fe80::200:50ff:fe3d:7aac) from fe80::204:23ff:fec8:9578 eth1: 56 data bytes 64 bytes from fe80::200:50ff:fe3d:7aac: icmp_seq=0 ttl=64 time=1.87 ms 64 bytes from fe80::200:50ff:fe3d:7aac: icmp_seq=1 ttl=64 time=0.162 ms $ snmpwalk udp6:'[fe80::200:50ff:fe3d:7aac]':161 sysUpTime SNMPv2-MIB::sysUpTime.0 = Timeticks: (46605) 0:07:46.05 $ snmpwalk udp6:'[fe80::200:50ff:fe3d:7aac]':161 sysUpTime Timeout: No Response from udp6:[fe80::200:50ff:fe3d:7aac]:161 What would cause this IPv6 query instability? Thanks for your support. Emi -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Dave Shield Sent: Monday, October 29, 2007 6:09 AM To: Emi Yanagi Cc: [email protected] Subject: Re: Failed to query IPv6 enabled snmpd remotely On 24/10/2007, Emi Yanagi <[EMAIL PROTECTED]> wrote: > But when I query remotely from a machine different than where snmpd is > running, I got "Unknown host" if using IPv6 address. > snmpwalk running on the remote machine doesn't have IPv6 enabled, but I > don't think it is needed, right? Wrong (I think). If you don't build the Net-SNMP library with IPv6 support enabled, then snmpwalk won't be able to use IPv6 addresses. Try re-compiling the tools to enable IPv6 and see if you get the same problem. Dave ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Net-snmp-coders mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
