You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When connecting to a node via external IP and the connection is forwarded to another node the connection should use the external IP of the new node.
Current Behavior
When attempting to connect to a service of type NodePort using the External IP of the node, if the workload endpoint is not currently on that node it will be forwarded using eBPF. Once forwarded the connection hangs in syn-sent due to packets with unknown source on the internal IP. Because the external connection is not able to communicate over the nodes private network it is not able to establish the connection.
Currently we are using eBPF and have DSR enabled. Even with DSR disabled and using tunnel instead the problem persists.
Steps to Reproduce (for bugs)
Deploy Calico to a K8S cluster with both External and Internal IP's with eBPF enabled and DSR enabled.
Expected Behavior
When connecting to a node via external IP and the connection is forwarded to another node the connection should use the external IP of the new node.
Current Behavior
When attempting to connect to a service of type NodePort using the External IP of the node, if the workload endpoint is not currently on that node it will be forwarded using eBPF. Once forwarded the connection hangs in
syn-sent
due topackets with unknown source
on the internal IP. Because the external connection is not able to communicate over the nodes private network it is not able to establish the connection.Currently we are using eBPF and have DSR enabled. Even with DSR disabled and using tunnel instead the problem persists.
Steps to Reproduce (for bugs)
enabled
and DSRenabled
.This request will hang if the nginx container is not running on the IP of the requested node.
Context
NAT Table
NAT table shows the correct backend for the frontend
Observed BPF forwarding requests which get hung on
syn-sent
On the counters we can see the packets being dropped on the internal interface:
tc output dropped:
External IP connection:
Internal IP connection:
Your Environment
The text was updated successfully, but these errors were encountered: