The IPv6 neigh sometimes entry into failed status and could not send package to the destination

rockju

1. My network topology as below, the pod node pull file from ftpserver as sftpclient every 5 minutes;
   

2. In normal cases, the pod learns the MAC address of the gateway routing node(2409:802f:5a06:120f::1009:181) through NDP NS packets, as shown in the following figure:
   

3. The ip -6 route list config as below:
   

4. My problem is that:
   The system intermittently fails to pull data from sftpserver. The cause is that the MAC address of the gateway node cannot be get by NDP NS message. According to the packet capture result of Wireshark, the SFTP tcp message does not trigger the NS message. The ip -6 neigh show command shows the neigh to the gateway node(2409:802f:5a06:120f::1009:181) status is failed. The error "No route to host" is reported on the SFTP application side, as shown in the following figure.

In normal cases, NS packets are triggered, as shown in the following figure：

When the problem occurs, the service side reports the following error.The ip -6 neigh show command shows the neigh to the gateway node(2409:802f:5a06:120f::1009:181) status is failed:

What could be the reason for this problem?

chrispokorni

Hi @rockju,

For a pod accessing an external server, you may need to configure an ExternalName Service or a Headless Service.

https://kubernetes.io/docs/concepts/services-networking/service/#publishing-services-service-types

Regards,
-Chris

rockju

Hi @chrispokorni ：

We dont visit the SFTP server by host, we visited by IPv6 address，so i think that only if the network is ok, we can visit the external server by pod, normally we could visit the sftpserver, sometimes couldnot visit.

Our pod deploy on VM, the pod use the VM eth2 port to visit the external server.