k3s flannel TCP fails if custom interface be used with --flannel-iface and TSO is off #10669
Unanswered
shakibamoshiri
asked this question in
Q&A
Replies: 2 comments
-
For the first test I used |
Beta Was this translation helpful? Give feedback.
0 replies
-
One more time testing again with veth and flannel does not send ? TCP (L4) but allows icmp (L3) |
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
-
I am trying to secure connection between two nodes (master and worker) with a layer 2 VPN.
The VPN server can connect to a bridge on each machine and k3s flannel with --flannel-iface vpn_interface can communicate
But the VPN server throughput is low if TSO (TCP Segmentation Offload) is on
So I tried to disable it
then while layer 2 and 3 are okay , I can ping other pods on worker node from master , but TCP faces timeout
Further checking with
tcpdump
showed that DF flag is on (Do not fragment)layer 3 (ping okay) from master to worker
layer 4 or 7 (netcat or curl failed) from master to worker
Thus turning TSO off (=disable) on the VPN bridge -- flannel cannot or disallows TCP !?
I should mention that I always use this VPN with a bridge and TSO is off and had no issue. which mean if there are a web server on worker node
netcat
orcurl
can talk withAny idea what is the root cause of this issue ?
Regards
Beta Was this translation helpful? Give feedback.
All reactions