Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BPF] send RST to midflow TCP packets from unknown streams #8933

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

tomastigera
Copy link
Contributor

Description

For a smooth switch from iptables to ebpf mode, we do not want to
interrupt existing connections. If we see midflow packets, we pass them
to the host stack. If the stack can verify that they belong to an
existing conntrack, we let them through and we learn the conntrack.

We drop the rest. However, there are some situations when we can see a
stray TCP packet during ebpf mode, for instance when a pod dies and ECMP
kicks in and sends a packet to a different host.

If such a packet gets dropped, the end of the connections remains stuck.
This change sends an RST to such a stream instead of just dropping the
packets so that the end host can break the connection.

Fixes #8882

Related issues/PRs

Todos

  • Tests
  • Documentation
  • Release note

Release Note

ebpf: don't drop, but reject unknown midflow tcp packets with rst 

Reminder for the reviewer

Make sure that this PR has the correct labels and milestone set.

Every PR needs one docs-* label.

  • docs-pr-required: This change requires a change to the documentation that has not been completed yet.
  • docs-completed: This change has all necessary documentation completed.
  • docs-not-required: This change has no user-facing impact and requires no docs.

Every PR needs one release-note-* label.

  • release-note-required: This PR has user-facing changes. Most PRs should have this label.
  • release-note-not-required: This PR has no user-facing changes.

Other optional labels:

  • cherry-pick-candidate: This PR should be cherry-picked to an earlier release. For bug fixes only.
  • needs-operator-pr: This PR is related to install and requires a corresponding change to the operator.

@tomastigera tomastigera requested a review from a team as a code owner June 20, 2024 21:31
@marvin-tigera marvin-tigera added this to the Calico v3.29.0 milestone Jun 20, 2024
@marvin-tigera marvin-tigera added release-note-required Change has user-facing impact (no matter how small) docs-pr-required Change is not yet documented labels Jun 20, 2024
@tomastigera tomastigera changed the title [BPF] send RST to midflow TCp packets from unknown streams [BPF] send RST to midflow TCP packets from unknown streams Jun 20, 2024
@tomastigera tomastigera force-pushed the tomas-bpf-spoof-tests branch 3 times, most recently from 22554ca to 546e370 Compare June 25, 2024 07:25
iptables.Rule{
Match: iptables.Match().MarkMatchesWithMask(tcdefs.MarkSeenFallThrough, tcdefs.MarkSeenFallThroughMask),
Comment: []string{fmt.Sprintf("%s packets from unknown flows.", d.ruleRenderer.IptablesFilterDenyAction())},
Comment: []string{fmt.Sprintf("%s packets from unknown TCP flows.", d.ruleRenderer.IptablesFilterDenyAction())},
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Comment: []string{fmt.Sprintf("%s packets from unknown TCP flows.", d.ruleRenderer.IptablesFilterDenyAction())},
Comment: []string{fmt.Sprintf("%s packets from unknown non-TCP flows.", d.ruleRenderer.IptablesFilterDenyAction())},

For a smooth switch from iptables to ebpf mode, we do not want to
interrupt existing connections. If we see midflow packets, we pass them
to the host stack. If the stack can verify that they belong to an
existing conntrack, we let them through and we learn the conntrack.

We drop the rest. However, there are some situations when we can see a
stray TCP packet during ebpf mode, for instance when a pod dies and ECMP
kicks in and sends a packet to a different host.

If such a packet gets dropped, the end of the connections remains stuck.
This change sends an RST to such a stream instead of just dropping the
packets so that the end host can break the connection.

Fixes projectcalico#8882
@tomastigera
Copy link
Contributor Author

only a single unrelated failure fixed here #8952

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
docs-pr-required Change is not yet documented release-note-required Change has user-facing impact (no matter how small)
Projects
None yet
Development

Successfully merging this pull request may close these issues.

eBPF not issuing TCP RST on unknown connections
3 participants