Skip to content
New issue

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

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

Already on GitHub? Sign in to your account

DNS dissector do not proceed next paket when receice CNAME #2575

Open
2 tasks done
didgaudin opened this issue Sep 30, 2024 · 1 comment
Open
2 tasks done

DNS dissector do not proceed next paket when receice CNAME #2575

didgaudin opened this issue Sep 30, 2024 · 1 comment
Labels

Comments

@didgaudin
Copy link

Describe the bug

When we receive 2 responses packets, if the first is cname, et second who contain de A record is not processed, and then flow->info do not contain protos.dns.rsp_addr.ipv4 value

Expected behavior

A clear and concise description of what you expected to happen.

Obtained behavior

A clear and concise description of what happening.

nDPI Environment (please complete the following information):

  • OS name: fedora
  • OS version: 41
  • Architecture: x86_64
  • nDPI version or commit hash: Using nDPI (4.11.0-4871-ddd08f9) [1 thread(s)]
  • nDPI compilation flags used:--with-pcre2 --with-local-libgcrypt]
  • Attach the config.log file generated after ./configure ran (if you are building from source).

How to reproduce the reported bug

Reproducible using ndpiReader?

  • The reported bug is reproducible using ndpiReader.
  • The reported bug is not reproducible using ndpiReader.

If applicable, the used ndpiReader options:

If your bug is reproducible using a pcap, please attach a pcap file (or a valid link to download it)

dns.pcap.gz

Example: dns.pcap.gz

Steps to reproduce the behavior:

  1. Run '...'
  2. Set '....'
  3. Do '....'
  4. See error

Additional context

Add any other context about the problem here.

@didgaudin didgaudin added the bug label Sep 30, 2024
@IvanNardi
Copy link
Collaborator

I acknowledge the problem.
However it is a little bit more complex that "skip any answers up to A/AAAA record" because we must be sure to return request metadata and answer metadata of the SAME transaction.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants