Skip to content

Conversation

jufajardini
Copy link
Contributor

It seems that in certain cases as seen in this test, flow.action isn't updated, even if, say, all packets from the flow are dropped.

Maybe this is due to the rule not being applied directly to the flow, but to each packet individually. But considering we are using a flow keyword, it seems that the engine should pass over the drop action to flow.action, at least in the flow event.

Bug #6976

Previous PR: #2007

Updates:

  • rebase
  • remove Suricata 6 checks

Ticket

If your pull request is related to a Suricata ticket, please provide
the full URL to the ticket here so this pull request can monitor
changes to the ticket status:

Redmine ticket:
https://redmine.openinfosecfoundation.org/issues/6976

It seems that in certain cases as seen in this test, flow.action isn't
updated, even if, say, all packets from the flow are dropped.

Maybe this is due to the rule not being applied directly to the flow,
but to each packet individually. But considering we are using a flow
keyword, it seems that the engine should pass over the drop action to
flow.action, at least in the flow event.

Bug #6976
@jufajardini jufajardini added the requires suricata fix This PR requires an issue in Suricata to be fixed first label Sep 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
requires suricata fix This PR requires an issue in Suricata to be fixed first
Development

Successfully merging this pull request may close these issues.

1 participant