Project

General

Profile

Actions

Bug #5115

closed

detect/ip_proto: inconsistent behavior when specifying protocol by string

Added by Jeff Lucovsky almost 3 years ago. Updated almost 3 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Target version:
Affected Versions:
Effort:
Difficulty:
Label:

Description

ip_proto:TCP will use getprotobyname, which may not work depending on the OS. E.g. in a docker Alpine it fails. We should probably just use a built-in table.


Related issues 1 (0 open1 closed)

Copied from Suricata - Bug #5072: detect/ip_proto: inconsistent behavior when specifying protocol by stringClosedJeff LucovskyActions
Actions

Also available in: Atom PDF