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.

Sign up for GitHub

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

Jump to bottom

When tcp requests syn, an incorrect ack is returned. When in the network quadruple, the source IP and port are the same, and the destination IP and port are different #29037

Closed
2 tasks done
llhhbc opened this issue Nov 8, 2023 · 9 comments
Closed
2 tasks done

When tcp requests syn, an incorrect ack is returned. When in the network quadruple, the source IP and port are the same, and the destination IP and port are different #29037

llhhbc opened this issue Nov 8, 2023 · 9 comments
Labels
info-completed The GH issue has received a reply from the author kind/bug This is a bug in the Cilium logic. kind/community-report This was reported by a user in the Cilium community, eg via Slack. needs/triage This issue requires triaging to establish severity and next steps. stale The stale bot thinks this issue is old. Add "pinned" label to prevent this from becoming stale.

Comments

@llhhbc
Copy link
Contributor

llhhbc commented Nov 8, 2023

Is there an existing issue for this?

  • I have searched the existing issues

What happened?

As shown in the figure below, two sessions: 10.82.36.11:40001 -> 10.82.107.128:3600 and 10.82.36.11:40001->10.82.107.120:3448. When the first one sends syn, the seq returned by the server is 1987538173 , when sending syn for the second session, the seq returned by the server is 1987538174, and cilium mistakenly treats the two sessions as one session.

企业微信截图_688b5251-7218-4197-b136-a264cc7f61e3

Cilium Version

1.12.7

Kernel Version

4.19.113-300.el7.x86_64

Kubernetes Version

1.24.10

Sysdump

No response

Relevant log output

No response

Anything else?

No response

Code of Conduct

  • I agree to follow this project's Code of Conduct
@llhhbc llhhbc added kind/bug This is a bug in the Cilium logic. kind/community-report This was reported by a user in the Cilium community, eg via Slack. needs/triage This issue requires triaging to establish severity and next steps. labels Nov 8, 2023
@squeed
Copy link
Contributor

squeed commented Nov 10, 2023

Where do you see the two sessions being combined? Are the conntrack maps indicating incorrect information?

@squeed squeed added the need-more-info More information is required to further debug or fix the issue. label Nov 10, 2023
@squeed
Copy link
Contributor

squeed commented Nov 10, 2023 •
edited

Also, Cilium is now up to v1.14.3; please consider upgrading. Likewise, it's difficult to consider issues without a sysdump or other debugging information.

@llhhbc
Copy link
Contributor Author

llhhbc commented Nov 12, 2023

the picture is the sysdump info, you can look the response seq. within in green and blue box,they are two session.

@github-actions github-actions bot added info-completed The GH issue has received a reply from the author and removed need-more-info More information is required to further debug or fix the issue. labels Nov 12, 2023
@llhhbc
Copy link
Contributor Author

llhhbc commented Nov 21, 2023

@squeed

@julianwiedmann
Copy link
Member

the picture is the sysdump info, you can look the response seq. within in green and blue box,they are two session.

Please follow the steps in the issue template:

Sysdump

Also please reproduce on the latest v1.12 release (which is currently v1.12.16). Or preferably v1.14.

@julianwiedmann julianwiedmann added need-more-info More information is required to further debug or fix the issue. and removed info-completed The GH issue has received a reply from the author labels Nov 21, 2023
@github-actions GitHub Actions
Copy link

This issue has been automatically marked as stale because it has not
had recent activity. It will be closed if no further activity occurs.

@github-actions github-actions bot added the stale The stale bot thinks this issue is old. Add "pinned" label to prevent this from becoming stale. label Jan 21, 2024
@github-actions GitHub Actions
Copy link

github-actions bot commented Feb 5, 2024

This issue has not seen any activity since it was marked stale.
Closing.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Feb 5, 2024
@llhhbc
Copy link
Contributor Author

llhhbc commented Feb 8, 2024

@julianwiedmann The results of the tcpdump packet capture clearly illustrate the problem. Is there no possible direction for the problem?

@llhhbc
Copy link
Contributor Author

llhhbc commented Feb 8, 2024

/reopen

@github-actions github-actions bot added info-completed The GH issue has received a reply from the author and removed need-more-info More information is required to further debug or fix the issue. labels Feb 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
info-completed The GH issue has received a reply from the author kind/bug This is a bug in the Cilium logic. kind/community-report This was reported by a user in the Cilium community, eg via Slack. needs/triage This issue requires triaging to establish severity and next steps. stale The stale bot thinks this issue is old. Add "pinned" label to prevent this from becoming stale.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@squeed @llhhbc @julianwiedmann