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

Use non-header-including byte size field for tcp connections #725

Open
2 tasks done
lisaSW opened this issue Mar 21, 2022 · 0 comments
Open
2 tasks done

Use non-header-including byte size field for tcp connections #725

lisaSW opened this issue Mar 21, 2022 · 0 comments
Assignees
@lisaSW

Comments

@lisaSW
Copy link
Contributor

lisaSW commented Mar 21, 2022 •
edited
Loading

Currently, the usage of orig_bytes/resp_bytes and orig_ip_bytes/resp_ip_bytes throughout the code is inconsistent. There is also a problem with beacon scores being skewed by variation in the header size of its connections

  • make usage of fields consistent
  • use orig_bytes/resp_bytes (header-excluding) for tcp connections, and orig_ip_bytes/resp_ip_bytes for all others
@lisaSW lisaSW self-assigned this Mar 21, 2022
@lisaSW lisaSW changed the title Use non-header including byte size field for tcp connections Use non-header-including byte size field for tcp connections Mar 21, 2022
@lisaSW lisaSW mentioned this issue Mar 21, 2022
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@lisaSW lisaSW

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Use non-header-including byte size field for tcp connections activecm/rita-legacy
1 participant
@lisaSW