On Tue, 6 Nov 2007 08:06:16 -0800
"Emi Yanagi" <[EMAIL PROTECTED]> wrote:
> 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
As you use a link-local address, why don't you attach the out-going
interface name to the target address?
$ snmpwalk udp6:'[fe80::200:50ff:fe3d:7aac%eth1]':161 sysUpTime
^^^^^
Best Regards,
----
Mitsuru Chinen <[EMAIL PROTECTED]>
-------------------------------------------------------------------------
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
