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

Cherry-pick #9891 to 6.6: [Netflow] Fix flow ID and locality calculation #9904

Merged
merged 1 commit into from
Jan 4, 2019

Conversation

adriansr
Copy link
Contributor

@adriansr adriansr commented Jan 4, 2019

Cherry-pick of PR #9891 to 6.6 branch. Original message:

Flow ID, Community ID and locality calculation was broken in the NetFlow input. 0.0.0.0 was always used as destination IP.

This caused:

  • The wrong flow-id and community-id to be generated
  • Different ids for the reverse-flow.
  • The wrong locality being assigned to the flow.

Flow ID, Community ID and locality calculation was broken in the
NetFlow input. 0.0.0.0 was always used as destination IP.

This caused:
- The wrong flow-id and community-id to be generated
- Different ids for the reverse-flow.
- The wrong locality being assigned to the flow.

(cherry picked from commit 511e74a)
@adriansr adriansr merged commit 7c6f87b into elastic:6.6 Jan 4, 2019
leweafan pushed a commit to leweafan/beats that referenced this pull request Apr 28, 2023
…c#9904)

Flow ID, Community ID and locality calculation was broken in the
NetFlow input. 0.0.0.0 was always used as destination IP.

This caused:
- The wrong flow-id and community-id to be generated
- Different ids for the reverse-flow.
- The wrong locality being assigned to the flow.

(cherry picked from commit 9821877)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants