tcpdump mailing list archives
Re: proposed change: make tcpdump -n and tcpdump -nn behave differently
From: Rick Jones <jonesrick () google com>
Date: Tue, 30 Oct 2018 09:04:16 -0700
My proverbial two cents is that is changing the semantics of an option, semantics which go back literally decades. New semantics should be associated with new options. On Tue, Oct 30, 2018 at 2:48 AM Denis Ovsienko <denis () ovsienko info> wrote:
Hello list. At https://github.com/the-tcpdump-group/tcpdump/pull/702 there is a simple proposed change, which seems to be an improvement: ------------------------- Subject: Introduce -nn option This changes the semantics on -n option so only namelookups are skipped. Port numbers *are* translated to their string representations. Option -nn then has the same semantics as -n had originally. This is a partial upstreaming of tcpdump-4.9.2-3 used in CentOs 7.5. ------------------------- If anybody sees how this change isn't an improvement, please make your point on the list. Thank you. -- Denis Ovsienko _______________________________________________ tcpdump-workers mailing list tcpdump-workers () lists tcpdump org https://lists.sandelman.ca/mailman/listinfo/tcpdump-workers
_______________________________________________ tcpdump-workers mailing list tcpdump-workers () lists tcpdump org https://lists.sandelman.ca/mailman/listinfo/tcpdump-workers
Current thread:
- proposed change: make tcpdump -n and tcpdump -nn behave differently Denis Ovsienko (Oct 30)
- Re: proposed change: make tcpdump -n and tcpdump -nn behave differently Rick Jones (Oct 30)
- Re: proposed change: make tcpdump -n and tcpdump -nn behave differently Joerg Mayer (Nov 04)