Project

General

Profile

Actions

Bug #1419

closed

DNS transaction handling issues

Added by Victor Julien over 7 years ago. Updated about 6 years ago.

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

Description

We don't properly handle the case where many requests are lost:
1. transaction_max not (always?) incremented
2. no 'request lost' flag


Related issues 1 (0 open1 closed)

Related to Bug #1664: Unreplied DNS queries not logged when flow is aged outClosedJason Ish01/07/2016Actions
Actions #1

Updated by Victor Julien over 7 years ago

  • Status changed from New to Assigned
  • Assignee set to Victor Julien
  • Target version changed from 2.1beta4 to 3.0RC1
Actions #2

Updated by Victor Julien almost 7 years ago

  • Target version changed from 3.0RC1 to 70
Actions #3

Updated by Victor Julien over 6 years ago

  • Priority changed from Normal to High
Actions #4

Updated by Jason Ish over 6 years ago

  • Related to Bug #1664: Unreplied DNS queries not logged when flow is aged out added
Actions #5

Updated by Jason Ish about 6 years ago

  • Status changed from Assigned to Closed
  • Target version changed from 70 to 3.1.1

Fixed. See https://github.com/inliniac/suricata/pull/2174

The use of different logger contexts for requests and replies should resolve this as the transaction log handling only concerns itself with a single direction, so lost messages should not affected future transactions.

Actions #6

Updated by Victor Julien about 6 years ago

  • Assignee changed from Victor Julien to Jason Ish
Actions

Also available in: Atom PDF