Actions
Feature #3292
closedsupport for network service header (NSH)
Effort:
Difficulty:
Label:
Protocol
Description
First part would be a dedicated protocol parser for NSH.
Second part would be to have some sort of integration within the engine based on the metainformation we receive from the NSH. One example might be deciding which tenant to use.
Another option for inline mode would be to add a flag to the packet that has been analyzed so another hop can investigate it.
Updated by Victor Julien about 5 years ago
For this ticket we will need actual use cases with pcaps and a description of the expected outcome.
Updated by Victor Julien about 5 years ago
- Status changed from New to Feedback
- Parent task deleted (
#3288)
Updated by Victor Julien about 5 years ago
- Related to Task #3288: Suricon 2019 brainstorm added
Updated by Victor Julien almost 4 years ago
- Status changed from Feedback to In Review
- Assignee changed from Community Ticket to Carl Smith
- Target version changed from TBD to 7.0.0-beta1
Updated by Victor Julien almost 4 years ago
- Status changed from In Review to Closed
Actions