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

[PcapPlusPlus Support]

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 easy-to-use interface to libpcap
but at the same time maintain libpcap's packet processing capabilities.
You can find out more about this project in PcapPlusPlus's web-site
.

I was browsing through the TCPDUMP/libpcap web-site and noticed a list
of related
projects . I was wondering if you'd
agree to add PcapPlusPlus to this list.

Please feel free to ask any questions you might have on PcapPlusPlus and
let me know what you think.

Thanks,
___
tcpdump-workers mailing list
tcpdump-workers@lists.tcpdump.org
https://lists.sandelman.ca/mailman/listinfo/tcpdump-workers

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

[Rick Jones]

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 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

Re: [tcpdump-workers] base directory for bluez

[Denis Ovsienko]

  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).
 > 
 > Unfortunately, the configure script uses an on/off switch for bluetooth
 > and tries to detect bluez in the default system directories. Would it
 > make sense to convert this to --with-bluetooth[=DIR]? 
 > 
 > Or is there already a mechanism to say that the bluetooth includes are
 > under $bluetooth_base/include and the libs are under
 > $bluetooth-base/lib?

Hello Martin.

Existing arrangements for DAG and SNF provide additional options to specify the 
libs and headers paths in addition to the library path, if required:

  --with-dag[=DIR]include Endace DAG support (located in directory
  DIR, if supplied). [default=yes, if present]
  --with-dag-includes=IDIR
  Endace DAG include directory, if not DIR/include
  --with-dag-libraries=LDIR
  Endace DAG library directory, if not DIR/lib

  --with-snf[=DIR]include Myricom SNF support (located in directory
  DIR, if supplied). [default=yes, if present]
  --with-snf-includes=IDIR
  Myricom SNF include directory, if not DIR/include
  --with-snf-libraries=LDIR
  Myricom SNF library directory, if not DIR/lib

Do you think the same would work best for cross-compiling with bluetooth 
support?

On a related note, since libpcap now uses both configure and cmake, the change 
to the options should be made in a similar way in both build props.

-- 
Denis Ovsienko


___
tcpdump-workers mailing list
tcpdump-workers@lists.tcpdump.org
https://lists.sandelman.ca/mailman/listinfo/tcpdump-workers

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

[Denis Ovsienko]

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