Asymmetric routing using mirrored network mode? #10730
Replies: 2 comments
-
I switched from VXLAN mode to Wireguard mode in Calico, but I still got the same result. All packets have a length of 0 going out. |
Beta Was this translation helpful? Give feedback.
0 replies
-
Closed in favor of #10842 |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
I saw this from my Kubernetes Pod in WSL2, running
curl 1.1.1.1
inside a pod as a result:10.244.75.137 being the Pod IP and 172.30.0.7 being the local NIC IP on the worker node. It seems like we have a case of asymmetric routing using mirrored network
I also saw it from tcpdump, all the packets initiated from the actions in the pod container will have a packet length of 0.
Capturing the Calico interface (the pod IP change a little, but the result is the same):
This is the result captured from running
curl 1.1.1.1
on the WSL shell (without getting into another k8s pod network namespace):I ran the same process except the WSL2 host instance is using bridged network mode:
So I ran
curl 1.1.1.1
in one of the pod specifically in a k8s node that runs bridged network...tcpdump from the pod NIC created by Calico:
Then this is pretty normal
Beta Was this translation helpful? Give feedback.
All reactions