Yutaro Hayakawa
Yutaro Hayakawa
Yes, once I confirm that changing string -> netip.Addr doesn't have any problem, I'll replace this PR with it.
Reworked in https://github.com/cilium/cilium/pull/21161. Let me close this PR.
I found this is a bug specific to the EKS ENI mode. ## TLDR iptables trace result ``` [ 3745.087686] TRACE: raw:CILIUM_PRE_raw:return:3 IN=lxcf6b49f5d512f OUT= MAC=06:2b:96:ba:ba:5f:0a:73:0a:93:f1:01:08:00 SRC=192.168.107.130 DST=192.168.105.232 LEN=60 TOS=0x00 PREC=0x00...
For the moment, the quick workaround would be only using 1-127 as a ClusterID. Let me think about how we can solve this.
@EricMountain Thanks for your info as well! > I suspect the bug is simply that the mask used in the iptable rule is incorect: it should be 0x8000 in order...
Connectivity test result for cluster-id=128 ``` 📋 Test Report ❌ 12/23 tests failed (26/114 actions), 0 tests skipped, 1 scenarios skipped: Test [allow-all-except-world]: ❌ allow-all-except-world/pod-to-pod/curl-0: cilium-test/client-7bdbddd7b-7rrzq (192.168.22.31) -> cilium-test/echo-same-node-7894f8ffcd-vws46 (192.168.110.77:8080)...
Maybe you retried 1. and succeeded? For 2. it seems it is a known flake (https://github.com/cilium/cilium/issues/21655). And I agree that it is not related to your changes. I think we...
Yeah, FRR ignores the `proto kernel` route, and there's no way to disable that behavior. I recently learned that some people rely on the route installed by Cilium (the one...
Hit a similar issue in v1.15: https://github.com/cilium/cilium/actions/runs/8251635069/job/22569181314