-
Notifications
You must be signed in to change notification settings - Fork 90
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
tests: linktype_name test #2023
base: master
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me, thanks :)
match: | ||
event_type: alert | ||
tunnel.dest_port: 4789 | ||
packet_info.linktype_name: RAW |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
By the way, @jlucovsky could we have packet_info.ethernet_type for your other PR ? ;-)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes -- it's on its way: OISF/suricata#11850
Issue: 6954 Ensure that the linktype_name is included in the alerts.
Issue: 4974 This commit extends the linktype_name validation across the existing tests so that more linktype name values are checked: - C_HDLC - PPP - IPV4 - IPV6 - RAW - EN10B - LINUX_SLL Some existing tests required suricata.yaml configuration to enable the packet values to be in the alerts.
Continuation of #2006
Issue: 6954
Ensure that the linktype_name is included in the alerts.
Updates:
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/6954
Suricata PR: OISF/suricata#11670