-
Notifications
You must be signed in to change notification settings - Fork 3.8k
Cilium ignores packets received on interface without default route set. #21192
Copy link
Copy link
Closed as not planned
Closed as not planned
Copy link
Labels
area/datapathImpacts bpf/ or low-level forwarding details, including map management and monitor messages.Impacts bpf/ or low-level forwarding details, including map management and monitor messages.kind/bugThis is a bug in the Cilium logic.This is a bug in the Cilium logic.kind/community-reportThis was reported by a user in the Cilium community, eg via Slack.This was reported by a user in the Cilium community, eg via Slack.need-more-infoMore information is required to further debug or fix the issue.More information is required to further debug or fix the issue.needs/triageThis issue requires triaging to establish severity and next steps.This issue requires triaging to establish severity and next steps.staleThe stale bot thinks this issue is old. Add "pinned" label to prevent this from becoming stale.The stale bot thinks this issue is old. Add "pinned" label to prevent this from becoming stale.
Description
Metadata
Metadata
Assignees
Labels
area/datapathImpacts bpf/ or low-level forwarding details, including map management and monitor messages.Impacts bpf/ or low-level forwarding details, including map management and monitor messages.kind/bugThis is a bug in the Cilium logic.This is a bug in the Cilium logic.kind/community-reportThis was reported by a user in the Cilium community, eg via Slack.This was reported by a user in the Cilium community, eg via Slack.need-more-infoMore information is required to further debug or fix the issue.More information is required to further debug or fix the issue.needs/triageThis issue requires triaging to establish severity and next steps.This issue requires triaging to establish severity and next steps.staleThe stale bot thinks this issue is old. Add "pinned" label to prevent this from becoming stale.The stale bot thinks this issue is old. Add "pinned" label to prevent this from becoming stale.
Is there an existing issue for this?
What happened?
Cilium ignores packets received on interface without default route set.
We have configuration with MetalLB in L2 mode and cilium in kube-proxy free mode.
External packets are coming into vlan interface with no IP assigned (metallb is used to announce arp from this interface)
The graphical scheme:
It is exactly case 3 described in my Configuring routing for MetalLB in L2 mode article.
Problem is that cilium only routes external packets received on 192.168.1.0/24 network.
External packets for 1.2.3.4 are ignored for some reason.
Node setup:
Cilium Version
v1.12.1
Kernel Version
5.4.0-86-generic
Kubernetes Version
v1.22.4
Sysdump
No response
Relevant log output
No response
Anything else?
No response
Code of Conduct