[tcpdump-workers] Possibility of adding PcapPlusPlus to tcpdump/libpcap related projects list

Hi, I'm the maintainer of an open source library called PcapPlusPlus which is a multiplatform C++ framework for packet processing and crafting. Among other things this library provides an extensive C++ wrapper for libpcap, which meant to be a simple and

Re: [tcpdump-workers] proposed change: make tcpdump -n and tcpdump -nn behave differently

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 wrote: > Hello list. > > At

Re: [tcpdump-workers] base directory for bluez

On Thu, 25 Oct 2018 14:57:48 +0100 Martin Kaiser wrote > Dear all, > > I'm trying to cross-compile libpcap and enable bluetooth support for it. > I've already cross-compiled bluez and installed it into a local > directory hierarchy (not under the cross-compiler's sysroot). >

[tcpdump-workers] proposed change: make tcpdump -n and tcpdump -nn behave differently

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*