leblancd / kube-v6

Instructions on how to instantiate a multi-node, IPv6-only Kubernetes cluster.
Apache License 2.0
168 stars 22 forks source link

Cannot ping ipv6 from remote container #7

Open bamb00 opened 6 years ago

bamb00 commented 6 years ago

I have a setup running Calico IPV6 enabled in Kubernetes v1.9.5 running docker 1.13.1-cs9. I'm not able to ping the remote container using ipv6 address. I can ping ipv6 address locally. Do you know what's needed to be resolve to be able to ping the remote container?

What is the best way to verify ipv6 traffic is coming into the container?


# kubectl get po -n kube-system
NAME                                                                  READY     STATUS    RESTARTS   AGE
calico-etcd-jg2vr                                                     1/1       Running   0          5h
calico-kube-controllers-866bf5646c-pplzf                              1/1       Running   0          5h
calico-node-kz2sk                                                     2/2       Running   0          5h
etcd-devtricorder0A-master-01                                         1/1       Running   0          5h
kube-apiserver-devtricorder0A-master-01                               1/1       Running   0          5h
kube-controller-manager-devtricorder0A-master-01                      1/1       Running   0          5h
kube-dns-6f4fd4bdf-zdwkz                                              3/3       Running   0          5h
kube-proxy-q9xg5                                                      1/1       Running   0          5h
kube-scheduler-devtricorder0A-master-01                               1/1       Running   0          5h
kubernetes-dashboard-68d7c968ff-nj2m7                                 1/1       Running   0          5h

From Container B: Pinging remote container

# ping6 fe80::e471:21ff:fef0:b88d
PING fe80::e471:21ff:fef0:b88d (fe80::e471:21ff:fef0:b88d): 56 data bytes
64 bytes from fe80::482b:91ff:fe64:de2b%eth0: Destination unreachable: Address unreachable
64 bytes from fe80::482b:91ff:fe64:de2b%eth0: Destination unreachable: Address unreachable
64 bytes from fe80::482b:91ff:fe64:de2b%eth0: Destination unreachable: Address unreachable
64 bytes from fe80::482b:91ff:fe64:de2b%eth0: Destination unreachable: Address unreachable
64 bytes from fe80::482b:91ff:fe64:de2b%eth0: Destination unreachable: Address unreachable
64 bytes from fe80::482b:91ff:fe64:de2b%eth0: Destination unreachable: Address unreachable

Pinging from locally

# ping6 fe80::482b:91ff:fe64:de2b
PING fe80::482b:91ff:fe64:de2b (fe80::482b:91ff:fe64:de2b): 56 data bytes
64 bytes from fe80::482b:91ff:fe64:de2b%eth0: icmp_seq=0 ttl=64 time=0.057 ms
64 bytes from fe80::482b:91ff:fe64:de2b%eth0: icmp_seq=1 ttl=64 time=0.060 ms
64 bytes from fe80::482b:91ff:fe64:de2b%eth0: icmp_seq=2 ttl=64 time=0.056 ms
64 bytes from fe80::482b:91ff:fe64:de2b%eth0: icmp_seq=3 ttl=64 time=0.059 ms
64 bytes from fe80::482b:91ff:fe64:de2b%eth0: icmp_seq=4 ttl=64 time=0.068 ms
64 bytes from fe80::482b:91ff:fe64:de2b%eth0: icmp_seq=5 ttl=64 time=0.053 ms

Container A:

# ip -6 addr show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 state UNKNOWN qlen 1000
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
4: eth0@if10: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1440 state UP
    inet6 fe80::e471:21ff:fef0:b88d/64 scope link
       valid_lft forever preferred_lft forever

# ip -6 route show
fe80::/64 dev eth0  proto kernel  metric 256

Container B:

# ip -6 addr show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 state UNKNOWN qlen 1000
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
4: eth0@if8: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1440 state UP
    inet6 fe80::482b:91ff:fe64:de2b/64 scope link
       valid_lft forever preferred_lft forever

# ip -6 route show
fe80::/64 dev eth0  proto kernel  metric 256
leblancd commented 6 years ago

@bamb00:

leblancd commented 6 years ago

@bamb00 - Any luck on the pings?