Project

General

Profile

Actions
Copy link

Bug #1419

closed
VJ JI

DNS transaction handling issues

Bug #1419: DNS transaction handling issues

Added by Victor Julien about 11 years ago. Updated almost 10 years ago.

Status:
Closed
Priority:
High
Assignee:
Jason Ish
Target version:
3.1.1
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 open — 1 closed)

Related to Suricata - Bug #1664: Unreplied DNS queries not logged when flow is aged outClosedJason IshActions

VJ Updated by Victor Julien almost 11 years ago Actions
Copy link
 #1

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

VJ Updated by Victor Julien over 10 years ago Actions
Copy link
 #2

  • Target version changed from 3.0RC1 to 70

VJ Updated by Victor Julien almost 10 years ago Actions
Copy link
 #3

  • Priority changed from Normal to High

JI Updated by Jason Ish almost 10 years ago Actions
Copy link
 #4

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

JI Updated by Jason Ish almost 10 years ago Actions
Copy link
 #5

  • 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.

VJ Updated by Victor Julien almost 10 years ago Actions
Copy link
 #6

  • Assignee changed from Victor Julien to Jason Ish
Actions
Copy link

Also available in: PDF Atom