We've been running ipv6 for a year or so now, but some of our newer
instances (all on an ESX cluster) are not working. It looks like it's
all of our Centos 6 instances. I'm hoping someone can point me in the
right direction...
tshark indicates that it's neighbor discovery that's failing:
<centos666.peak.org> [38] # tshark -n -i eth0 ip6
Running as user "root" and group "root". This could be dangerous.
Capturing on eth0
0.000000 2607:f678::16:66 -> ff02::1:ff00:1 ICMPv6 Neighbor solicitation
1.000019 2607:f678::16:66 -> ff02::1:ff00:1 ICMPv6 Neighbor solicitation
2.000043 2607:f678::16:66 -> ff02::1:ff00:1 ICMPv6 Neighbor solicitation
4.001030 2607:f678::16:66 -> ff02::1:ff00:1 ICMPv6 Neighbor solicitation
5.001076 2607:f678::16:66 -> ff02::1:ff00:1 ICMPv6 Neighbor solicitation
6.001045 2607:f678::16:66 -> ff02::1:ff00:1 ICMPv6 Neighbor solicitation
^C6 packets captured
A centos 5.8 vm with the same virtual network connections works fine:
<ns6.peak.org> [103] # ping6 2607:f678::1
PING 2607:f678::1(2607:f678::1) 56 data bytes
64 bytes from 2607:f678::1: icmp_seq=0 ttl=64 time=1.34 ms
64 bytes from 2607:f678::1: icmp_seq=1 ttl=64 time=0.894 ms
64 bytes from 2607:f678::1: icmp_seq=2 ttl=64 time=0.871 ms
--- 2607:f678::1 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2001ms
rtt min/avg/max/mdev = 0.871/1.035/1.342/0.219 ms, pipe 2
<ns6.peak.org> [104] # ping6 ipv6.google.com
PING ipv6.google.com(pz-in-x67.1e100.net) 56 data bytes
64 bytes from pz-in-x67.1e100.net: icmp_seq=0 ttl=52 time=14.1 ms
64 bytes from pz-in-x67.1e100.net: icmp_seq=1 ttl=52 time=14.3 ms
64 bytes from pz-in-x67.1e100.net: icmp_seq=2 ttl=52 time=14.3 ms