Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

#

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Jump to bottom

Ensure correctness of reported traffic direction #39

Closed
klingerko opened this issue Mar 19, 2019 · 0 comments
Closed

Ensure correctness of reported traffic direction #39

klingerko opened this issue Mar 19, 2019 · 0 comments
Assignees
@satta
Labels
enhancement New feature or request

Comments

@klingerko
Copy link

klingerko commented Mar 19, 2019 •
edited by satta
Loading

In some cases the name of the signature does not match the reported traffic direction (e.g. Signature name is "bad DNS lookup" but in fact a DNS response from a server to a requesting client is reported). We should check whether the events belongs to a DNS query or response and print then "lookup" or "reply" as signature message.
@satta satta changed the title Ensure correctness of presented Traffic direction Ensure correctness of reported traffic direction Mar 19, 2019
@satta satta self-assigned this Mar 19, 2019
@satta satta added the enhancement New feature or request label Mar 19, 2019
@satta satta mentioned this issue Mar 19, 2019
Merged
# for free to join this conversation on GitHub. Already have an account? # to comment
Assignees

@satta satta

Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@satta @klingerko