lou-lan

I am working on the reproduction, and I will provide updates as soon as there is progress.

Try the new v0.6.7 version — we’ve fixed several recently discovered issues (including the one caused by rp_filter). If any problems arise, please feel free to reopen it.

@bayooow Hi, can you provide the follow information ```shell kubectl get nodes -o wide kubectl get egt -o wide kubectl pods -o wide -A | grep your_app_name kubectl get egresspolicy...

@bayooow I am check iptables.log file, and it seems that Calico iptables rule has the highest priority, causing the egress iptables rules to not take effect. However, I’m not sure...

The priority of Calico iptables needs to be adjusted through the Calico settings. Can you provide the following information again? 1. FelixConfiguration YAML ```yaml kubectl get FelixConfiguration -o yaml apiVersion:...

> hey @lou-lan > > i try to run command iptables -t mangle -nvL PREROUTING on worker host. here's the result, > > ``` > Chain PREROUTING (policy ACCEPT 2576K...

@bayooow We fixed the issue regarding the selection of the parent network interface for VXLAN in the PR at https://github.com/spidernet-io/egressgateway/pull/1431. You can upgrade to v0.6.0 to test it out. You...

> I have upgraded to version 0.6.0, but the same issue persists @lou-lan Can you ping and try to tcpdump packet ? ``` Node1 ---- ping -----> Node2-VXLAN-IP ``` ```...

> @lou-lan > > I just realized that the EGT that can't be pinged is only on the egressgateway node. If I ping other egt, the ping succeeds. @bayooow *...

@bayooow Now look you egress vxlan tunnel is work when you delete tuunel after. I am checked you `EgressPolicy` used IP `172.18.38.186`, is it conflict you `node1` ip address, both...