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

[RFC] More user-friendly verbose output for DNS flags #445

Open
msekletar opened this issue Mar 25, 2015 · 5 comments
Open

[RFC] More user-friendly verbose output for DNS flags #445

msekletar opened this issue Mar 25, 2015 · 5 comments

Comments

@msekletar
Copy link
Contributor

Hi everyone,

I've received complaint from user in bugzilla that it is difficult to distinguish DNS response which has f.e. AD bit set. Right know tcpdump will produce following output for DNS response having AD bit set,

09:35:59.377000 IP localhost.domain > localhost.43144: 20972$ 3/6/13 SSHFP, RRSIG, RRSIG (3012)

Note $ character appearing after the transaction ID. Basically question is if tcpdump should provide alternative output to this, i.e. 20972 [AD] if verbose is set?

I think it would be reasonable to do that because dissector output is not documented anywhere afaik and you have to look to the source code of the dissector to find out what $ character actually means.

https://bugzilla.redhat.com/show_bug.cgi?id=1164048

@infrastation
Copy link
Member

Man page maybe?

@infrastation
Copy link
Member

Allright, the original report explains that tcpdump only displays 2 of the 3 flags, and for DNS responses only and requests that tcpdump displays all 3 flags and for both directions and uses the existing AD/DO/CD namespace instead of its own.

@msekletar
Copy link
Contributor Author

Should I prepare patch adding support for 3rd flag and introduce new ouput then?

@infrastation
Copy link
Member

That is a good idea, this at least can put the intended changes into the discussion scope.

@infrastation
Copy link
Member

Update: tcpdump actually prints the EDNS DO bit if given -vv argument.

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

No branches or pull requests

2 participants