Project

General

Profile

Actions

Feature #3546

closed

Teredo port configuration

Added by Victor Julien about 4 years ago. Updated almost 4 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Target version:
Effort:
Difficulty:
Label:
Needs backport to 5.0, Protocol

Description

Teredo tunnel detection is difficult because of the protocol which is too limited.

To avoid miss detection, we can had a port parameter to avoid to run the detection on all flow. The configuration could look like that:

tunnel
  - teredo:
    enabled: yes|no
    ports: port1,port2|any

This ticket is about adding the port configuration.


Related issues 2 (0 open2 closed)

Copied from Suricata - Feature #744: Teredo configurationClosedVictor Julien02/01/2013Actions
Copied to Suricata - Feature #3613: Teredo port configurationClosedJeff LucovskyActions
Actions

Also available in: Atom PDF