Bug #1419
closed
DNS transaction handling issues
Added by Victor Julien about 9 years ago.
Updated almost 8 years ago.
Description
We don't properly handle the case where many requests are lost:
1. transaction_max not (always?) incremented
2. no 'request lost' flag
- Status changed from New to Assigned
- Assignee set to Victor Julien
- Target version changed from 2.1beta4 to 3.0RC1
- Target version changed from 3.0RC1 to 70
- Priority changed from Normal to High
- Related to Bug #1664: Unreplied DNS queries not logged when flow is aged out added
- 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.
- Assignee changed from Victor Julien to Jason Ish
Also available in: Atom
PDF