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

detect: Recognize ERSPAN Type I packets #4466

Closed
wants to merge 2 commits into from

Conversation

jlucovsky
Copy link
Contributor

@jlucovsky jlucovsky commented Dec 28, 2019

This PR adds support for ERSPAN Type I packets.

This document and wireshark were used as a reference for this work.

Link to redmine ticket:3422

Describe changes:

  • Recognize ERSPAN Type I packets
  • Misc. typo/spelling corrections

Suricata-verify pr 169

@@ -890,6 +890,7 @@ void CaptureStatsSetup(ThreadVars *tv, CaptureStats *s);
enum DecodeTunnelProto {
DECODE_TUNNEL_ETHERNET,
DECODE_TUNNEL_ERSPAN,
DECODE_TUNNEL_ERSPAN_TYPEI,
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

So is our default ERSPAN actually type 2? Maybe we can just name these DECODE_TUNNEL_ERSPAN2 and DECODE_TUNNEL_ERSPAN1 then?

/**
* \brief ERSPAN Type I
*/
int DecodeERSPANTypeI(ThreadVars *tv, DecodeThreadVars *dtv, Packet *p, const uint8_t *pkt, uint32_t len, PacketQueue *pq)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

For new code, lets make sure we wrap lines.

@jlucovsky
Copy link
Contributor Author

Continued in #4474

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

2 participants