> There are many open issues about this across multiple repos, but you can follow the thread from here: [#1266 (comment)](https://github.com/rancher/k3s/issues/1266#issuecomment-640415989)

[Bowser1704]

There are many open issues about this across multiple repos, but you can follow the thread from here: rancher/k3s#1266 (comment)

tl;dr vxlan is broken at the moment due to a kernel bug; you can either switch to host-gw or work around it by running an ethtool command (that needs to be re-run every time hosts are rebooted) on every node.

thanks.
I changed the flannel backend from vxlan to host-gw, but it doesn't seem to work.

• method to change flannel backend.

vim /etc/systemd/system/k3s.service

• what I modified.

ExecStart=/usr/local/bin/k3s server --flannel-backend host-gw

• restart k3s

systemctl daemon-reload
systemctl restart k3s

• check my k3s net-conf

[root@bowser1704 ~]# cat /var/lib/rancher/k3s/agent/etc/flannel/net-conf.json
{
	"Network": "10.42.0.0/16",
	"Backend": {
	"Type": "host-gw"
}
}

But it still doesn't work.

[root@bowser1704 ~]# kubectl get svc -n food
NAME           TYPE        CLUSTER-IP      EXTERNAL-IP   PORT(S)    AGE
redis          ClusterIP   10.43.105.118   <none>        7388/TCP   48d
food-backend   ClusterIP   10.43.105.114   <none>        8080/TCP   48d
[root@bowser1704 ~]# curl http://10.43.105.114:8080/sd/health
^C
[root@bowser1704 ~]# kubectl get ep -n food
NAME           ENDPOINTS         AGE
food-backend   10.42.1.4:8080    48d
redis          10.42.0.10:6388   48d
[root@bowser1704 ~]# curl http://10.42.1.4:8080/sd/health
OK
[root@bowser1704 ~]#

Do you have any suggestions?
thanks.

Originally posted by @Bowser1704 in #1958 (comment)