Re: [tcpdump-workers] tcpdump testsuite and Perl

2020-01-29 Thread Denis Ovsienko via tcpdump-workers
--- Begin Message --- On Wed, 29 Jan 2020 10:59:14 +0100 Francois-Xavier Le Bail wrote: > On 28/01/2020 23:17, Denis Ovsienko via tcpdump-workers wrote: > > The new dependency makes it more difficult to run tests and will > > break package builds downstream (thus penalising pe

Re: [tcpdump-workers] tcpdump testsuite and Perl

2020-01-28 Thread Denis Ovsienko via tcpdump-workers
--- Begin Message --- > Currently on OpenCSW Solaris 10: > > "./tests/TESTrun > TESTrun needs YAML.pm. apt install libyaml-perl/yum install > per-YAML/cpanm YAML at ./tests/TESTrun line 10. > gmake: *** [Makefile:448: check] Error 2" > > Missing package? The new dependency makes it more

Re: [tcpdump-workers] moving tcpdump from sbindir to bindir

2020-09-10 Thread Denis Ovsienko via tcpdump-workers
--- Begin Message --- On Thu, 27 Aug 2020 12:58:10 +0100 Denis Ovsienko via tcpdump-workers wrote: > Hello list. > > tcpslice master branch now installs the binary into bindir instead of > sbindir, see [1]. Guy had suggested to make the same change in > tcpdump. [...] The a

Re: [tcpdump-workers] [tcpdump] After setjmp/longjmp update

2020-09-07 Thread Denis Ovsienko via tcpdump-workers
--- Begin Message --- On Mon, 7 Sep 2020 17:26:28 +0200 Francois-Xavier Le Bail wrote: > On 07/09/2020 16:43, Denis Ovsienko via tcpdump-workers wrote: > > On Sat, 5 Sep 2020 18:20:42 +0200 > > Thank you for posting a detailed explanation and making the first > > round of

[tcpdump-workers] libpcap detection and linking in tcpdump

2020-09-09 Thread Denis Ovsienko via tcpdump-workers
--- Begin Message --- Hello list. Travis CI tcpdump builds have been failing for a while and I went to see why. It is easy to see that only the jobs that have "BUILD_LIBPCAP=yes CMAKE=yes" fail, for example [1], and the same jobs built well before, for example [2]. The tcpdump build process

Re: [tcpdump-workers] DLT for RFtap

2020-09-12 Thread Denis Ovsienko via tcpdump-workers
--- Begin Message --- On Fri, 11 Sep 2020 16:59:19 +0200 George Hopkins via tcpdump-workers wrote: > Hello > > A few years ago there was a request to assign a DLT for RFtap [1]: > https://lists.sandelman.ca/pipermail/tcpdump-workers/2016-August/000619.html > > Somehow some of the messages

Re: [tcpdump-workers] [tcpdump] After setjmp/longjmp update

2020-09-12 Thread Denis Ovsienko via tcpdump-workers
--- Begin Message --- On Sat, 5 Sep 2020 18:20:42 +0200 Francois-Xavier Le Bail via tcpdump-workers wrote: [...] > We have: > 1) The "old" way, before the patch, returning from all functions and > at the end returning the header length to the link-layer dissector > (xxx_if_print), updating the

Re: [tcpdump-workers] [tcpdump] After setjmp/longjmp update

2020-09-07 Thread Denis Ovsienko via tcpdump-workers
--- Begin Message --- On Sat, 5 Sep 2020 18:20:42 +0200 Francois-Xavier Le Bail via tcpdump-workers wrote: Hello Francois-Xavier. Thank you for posting a detailed explanation and making the first round of changes. I am looking into the logic of this work. As soon as it feels I can tell the

Re: [tcpdump-workers] libpcap error codes?

2020-10-07 Thread Denis Ovsienko via tcpdump-workers
--- Begin Message --- On Wed, 7 Oct 2020 14:37:41 -0700 Guy Harris via tcpdump-workers wrote: [...] > A new API could be added that returns a PCAP_ERROR_ value rather than > -1 on error (so as not to break source or binary compatibility with > code using the existing APIs). Do you mean to

[tcpdump-workers] strlcpy() in tcpslice

2020-08-25 Thread Denis Ovsienko via tcpdump-workers
--- Begin Message --- Hello list. The most recent commit to tcpslice (e3d63a6) has traded one cppcheck warning to another: -[tcpslice.c:999]: (style) Obsolete function 'asctime' called. It is recommended to use 'strftime' instead. +[missing/strlcpy.c:46]: (style) The function 'strlcpy' is never

Re: [tcpdump-workers] tcpslice licence

2020-08-17 Thread Denis Ovsienko via tcpdump-workers
--- Begin Message --- On Mon, 3 Aug 2020 13:22:35 -0700 Guy Harris wrote: [...] > The first step I'd take would be to get rid of the GPLed headers in > favor of BSD-licensed headers, e.g. taking the ip.h, tcp.h, and udp.h > headers from tcpdump and changing the code to work with them. [...] I

[tcpdump-workers] tcpslice 1.3 is coming up

2020-08-18 Thread Denis Ovsienko via tcpdump-workers
--- Begin Message --- Hello list. Tcpslice master branch contains a number of long overdue improvements, please see the "1.3" secton at [1]. In order to progress [2] towards a resolution, let me suggest to make release 1.3 anytime soon. For clarity, it would not be entirely correct to call this

[tcpdump-workers] tcpdump continuous integration matters

2020-08-18 Thread Denis Ovsienko via tcpdump-workers
--- Begin Message --- Hello again. FreeBSD 13 task of Cirrus CI tcpdump build is currently broken, here is the support request: https://github.com/cirruslabs/cirrus-ci-docs/issues/695 If anybody has a good idea how to fix it long-term, please comment here or in the request above, wherever you

Re: [tcpdump-workers] tcpdump continuous integration matters

2020-08-21 Thread Denis Ovsienko via tcpdump-workers
--- Begin Message --- On Wed, 19 Aug 2020 00:51:11 +0100 Denis Ovsienko via tcpdump-workers wrote: [...] > Also, the current Travis CI build matrix expands to 108 (!) jobs, so > if you are making a trivial commit (such as in the man pages or the > documentation), please remember to sk

[tcpdump-workers] backward compatibility in pcap_loop(3PCAP)?

2020-08-21 Thread Denis Ovsienko via tcpdump-workers
--- Begin Message --- Hi. The man page says: (In older versions of libpcap, the behavior when cnt was 0 was undefined; different platforms and devices behaved differently, so code that must work with older versions of libpcap should use -1, not 0, as the value

Re: [tcpdump-workers] backward compatibility in pcap_loop(3PCAP)?

2020-08-22 Thread Denis Ovsienko via tcpdump-workers
--- Begin Message --- > That's where other "some of what this manual page says doesn't apply > to older versions of libpcap" items go, so it'd make sense. Alright, that's done now, thanks! -- Denis Ovsienko --- End Message --- ___ tcpdump-workers

[tcpdump-workers] moving tcpdump from sbindir to bindir

2020-08-27 Thread Denis Ovsienko via tcpdump-workers
--- Begin Message --- Hello list. tcpslice master branch now installs the binary into bindir instead of sbindir, see [1]. Guy had suggested to make the same change in tcpdump. I have asked tcpdump package maintainers of Debian, Fedora, Gentoo and SUSE, they all have confirmed they would be OK

Re: [tcpdump-workers] Using libnetdissect in other code, outside tcpdump source tree

2020-08-24 Thread Denis Ovsienko via tcpdump-workers
--- Begin Message --- On Wed, 12 Aug 2020 13:31:36 -0700 Guy Harris via tcpdump-workers wrote: [...] > > Also, netdissect.h likes to #define min() and max() macros, which > > makes life interesting when you have, say, a struct with min and > > max elements. > > It should probably define

Re: [tcpdump-workers] [tcpdump] After setjmp/longjmp update

2020-09-24 Thread Denis Ovsienko via tcpdump-workers
--- Begin Message --- On Thu, 17 Sep 2020 15:15:25 +0100 Denis Ovsienko via tcpdump-workers wrote: > On Sat, 5 Sep 2020 18:20:42 +0200 > Francois-Xavier Le Bail via tcpdump-workers > wrote: > > > 2) Process all the truncated cases with: > > ndo->ndo_ll_h

Re: [tcpdump-workers] [tcpdump] After setjmp/longjmp update

2020-09-24 Thread Denis Ovsienko via tcpdump-workers
--- Begin Message --- On Fri, 18 Sep 2020 10:25:13 +0200 Francois-Xavier Le Bail wrote: [...] > switch (setjmp(ndo->early_end)) { > case 0: > /* Print the packet. */ > (ndo->ndo_if_printer)(ndo, h, sp); > break; > case

Re: [tcpdump-workers] [tcpdump] After setjmp/longjmp update

2020-09-24 Thread Denis Ovsienko via tcpdump-workers
--- Begin Message --- On Sat, 5 Sep 2020 18:20:42 +0200 Francois-Xavier Le Bail via tcpdump-workers wrote: [...] > 2) Process all the truncated cases with: > ndo->ndo_ll_hdr_len = 0; > longjmp(ndo->ndo_truncated, 1); > (With a new macro, like 'ND_TRUNCATED' or 'ND_IS_TRUNCATED') [...] It could

Re: [tcpdump-workers] [tcpdump] After setjmp/longjmp update

2020-09-26 Thread Denis Ovsienko via tcpdump-workers
--- Begin Message --- On Fri, 25 Sep 2020 03:04:21 +0100 Denis Ovsienko via tcpdump-workers wrote: [...] > == Summary: the method seems to work well, there is a clean reference > implementation, it should be easy to apply to other printers that > implement similar encodings,

Re: [tcpdump-workers] [tcpdump] After setjmp/longjmp update

2020-09-18 Thread Denis Ovsienko via tcpdump-workers
--- Begin Message --- On Fri, 18 Sep 2020 10:25:13 +0200 Francois-Xavier Le Bail wrote: [...] > Or perhaps better (no need for a 'early_end_reason' field): > switch (setjmp(ndo->early_end)) { > case 0: > /* Print the packet. */ >

Re: [tcpdump-workers] [tcpdump] After setjmp/longjmp update

2020-09-17 Thread Denis Ovsienko via tcpdump-workers
--- Begin Message --- On Thu, 17 Sep 2020 22:05:30 +0200 Francois-Xavier Le Bail wrote: [...] > Should we have something like: > > if (setjmp(ndo->early_end) == 0) { > /* Print the packet. */ > (ndo->ndo_if_printer)(ndo, h, sp); > } else { >

Re: [tcpdump-workers] [tcpdump] After setjmp/longjmp update

2020-09-17 Thread Denis Ovsienko via tcpdump-workers
--- Begin Message --- On Sat, 5 Sep 2020 18:20:42 +0200 Francois-Xavier Le Bail via tcpdump-workers wrote: > 2) Process all the truncated cases with: > ndo->ndo_ll_hdr_len = 0; > longjmp(ndo->ndo_truncated, 1); > (With a new macro, like 'ND_TRUNCATED' or 'ND_IS_TRUNCATED') The master branch now

[tcpdump-workers] tcpslice licence

2020-08-03 Thread Denis Ovsienko via tcpdump-workers
--- Begin Message --- Hello list. Whilst updating the description of files in tcpslice (the little relative of tcpdump) repository, it came to my attention that it does not have the customary LICENSE file. I have looked through the .c and .h files and they contain the following boilerplates: * a

Re: [tcpdump-workers] Using tcpdump to decrypt IPSec ESP sessions (none and aes-cbc)

2020-08-06 Thread Denis Ovsienko via tcpdump-workers
--- Begin Message --- On Thu, 6 Aug 2020 11:19:21 -0600 Philip Prindeville via tcpdump-workers wrote: > Hi. > > I’m trying to debug a Strongswan config and wanted to verify that my > GRE traffic is being encapsulated properly by IPSec. “Tcpdump” to > the rescue. Well, almost. > > So I was

[tcpdump-workers] tcpslice releases, branches and tags

2020-08-12 Thread Denis Ovsienko via tcpdump-workers
--- Begin Message --- Hello all. Here is what I managed to establish from the LBL tcpslice tarballs and the-tcpdump-group/tclslice git repository: * The master branch has only one commit that at least loosely corresponds to an LBL release, that is 9d55298 and tcpslice-1.1a3.tar.Z

[tcpdump-workers] pcap_compile_nopcap() not in man pages

2020-08-12 Thread Denis Ovsienko via tcpdump-workers
--- Begin Message --- Hello list. It turns out, pcap_compile_nopcap() has been a part of the libpcap API since version 0.5 (June 2000), but it is not even mentioned anywhere in the man pages. The existing pcap_compile.3pcap man page seems to be the best place to add this information, since the

[tcpdump-workers] pcap_compile_nopcap() not in man pages (2nd attempt)

2020-08-12 Thread Denis Ovsienko via tcpdump-workers
--- Begin Message --- Hello list. It turns out, pcap_compile_nopcap() has been a part of the libpcap API since version 0.5 (June 2000), but it is not even mentioned anywhere in the man pages. The existing pcap_compile.3pcap man page seems to be the best place to add this information, since the

[tcpdump-workers] tcpslice releases, branches and tags (2nd attempt)

2020-08-12 Thread Denis Ovsienko via tcpdump-workers
--- Begin Message --- Hello all. Here is what I managed to establish from the LBL tcpslice tarballs and the-tcpdump-group/tclslice git repository: * The master branch has only one commit that at least loosely corresponds to an LBL release, that is 9d55298 and tcpslice-1.1a3.tar.Z

Re: [tcpdump-workers] Custom decoding offset? (for batman-adv)

2020-11-06 Thread Denis Ovsienko via tcpdump-workers
--- Begin Message --- On Fri, 6 Nov 2020 14:34:12 +0100 Linus Lüssing via tcpdump-workers wrote: [...] > Which suggests something like: > > $ tcpdump -i eth0 -w - | editcap -C 82 - - | tcpdump -r - > > However, ideally I would like to use a custom offset in a project > based on libpcap: > >

[tcpdump-workers] tcpdump build doc for Windows

2021-01-03 Thread Denis Ovsienko via tcpdump-workers
--- Begin Message --- Hello list. tcpdump source tree has a short file named "Readme.Win32", which was mostly updated on 8 Aug 2019, and a longer file named "doc/README.Win32.md", which was mostly updated on 5 Feb 2020. These seem to provide somewhat different instructions, perhaps it would be a

Re: [tcpdump-workers] tcpdump build doc for Windows

2021-01-03 Thread Denis Ovsienko via tcpdump-workers
--- Begin Message --- On Sun, 3 Jan 2021 14:23:40 -0800 Guy Harris wrote: [...] > They're both reasonably up-to-date (they both mention Npcap and the > use of CMake), but the latter is more detailed. > > I'll check whether the first document says anything that's not > mentioned in the second,

Re: [tcpdump-workers] [tcpdump] After setjmp/longjmp update

2021-01-05 Thread Denis Ovsienko via tcpdump-workers
--- Begin Message --- On Mon, 4 Jan 2021 12:35:29 -0500 Bill Fenner via tcpdump-workers wrote: > I just wanted to share some of my thinking about how to proceed with > the truncation-related changes on the road to 5.0.0. > > 1. Improve code coverage for the printer that's being modified. (This

Re: [tcpdump-workers] libpcap detection and linking in tcpdump

2021-01-07 Thread Denis Ovsienko via tcpdump-workers
--- Begin Message --- On Thu, 7 Jan 2021 16:46:41 -0800 Guy Harris wrote: > 3.1 dates back to 2015. That might be sufficient to treat as a > minimum. 5 years of backward compatibility might be OK'ish, although from time to time I run into such "long-term support" systems that in practice mean

Re: [tcpdump-workers] Stick with Travis for continuous integration, or switch?

2021-01-20 Thread Denis Ovsienko via tcpdump-workers
--- Begin Message --- On Mon, 18 Jan 2021 22:29:21 -0800 Guy Harris via tcpdump-workers wrote: > Travis CI is announcing on the travis-ci.org site that "... > travis-ci.org will be shutting down in several weeks, with all > accounts migrating to travis-ci.com. Please stay tuned here for more >

Re: [tcpdump-workers] Stick with Travis for continuous integration, or switch?

2021-01-21 Thread Denis Ovsienko via tcpdump-workers
--- Begin Message --- On Thu, 21 Jan 2021 08:15:33 +0100 Dagobert Michelsen wrote: > Hi folks, > > Am 21.01.2021 um 04:24 schrieb Denis Ovsienko via tcpdump-workers > : > >>s390x (a/k/a z/Architecture, i.e. S/3x0-64) - a big-endian > >> platform, so we ca

[tcpdump-workers] longjmp() conversion progress

2021-01-15 Thread Denis Ovsienko via tcpdump-workers
--- Begin Message --- Hello list. As a follow-up to the comments Bill had made a few days ago, please find below the current progress of the longjmp() conversion, which was earlier discussed in great detail on the list. I might post updated versions of this report in future if (and only if) there

Re: [tcpdump-workers] libpcap detection and linking in tcpdump

2021-01-22 Thread Denis Ovsienko via tcpdump-workers
--- Begin Message --- On Wed, 9 Sep 2020 17:07:25 +0100 Denis Ovsienko via tcpdump-workers wrote: > Here are my steps to reproduce: > > libpcap$ ./configure --enable-remote --prefix=/tmp/libpcap > libpcap$ make > libpcap$ make install > tcpdumpbuild$ cmake

Re: [tcpdump-workers] Stick with Travis for continuous integration, or switch?

2021-02-01 Thread Denis Ovsienko via tcpdump-workers
--- Begin Message --- On Mon, 18 Jan 2021 22:29:21 -0800 Guy Harris via tcpdump-workers wrote: > I guess we meet those requirements, although I'm not too keen on > having to keep going hat-in-hand to them every time we run out of > credits; hopefully, we can just get a renewable amount. I had

Re: [tcpdump-workers] CI status update

2021-05-06 Thread Denis Ovsienko via tcpdump-workers
--- Begin Message --- On Mon, 5 Apr 2021 10:42:39 +0100 Denis Ovsienko via tcpdump-workers wrote: > Hello list. > > I hope you have a great day. Please find below a brief overview of > some current continuous integration matters. Please find below a few recent developments si

[tcpdump-workers] CI news June 2021

2021-06-26 Thread Denis Ovsienko via tcpdump-workers
--- Begin Message --- Hello list. I hope you have a nice summer weekend. Below you can find a digest of improvements made in the Buildbot infrastructure in the last couple months. * After some OS shuffling one more worker had moved from my home lab to OSU OSL. As a result, linux-aarch64 became

Re: [tcpdump-workers] Stick with Travis for continuous integration, or switch?

2021-01-28 Thread Denis Ovsienko via tcpdump-workers
--- Begin Message --- On Mon, 18 Jan 2021 22:29:21 -0800 Guy Harris via tcpdump-workers wrote: > So we can either migrate to travis-ci.com or use other providers. Travis has been downsizing the .org server pool for a couple weeks, so far it has went from 370 to 250 with apparent effect on the

Re: [tcpdump-workers] ARM build slaves (tcpdump mirror in Germany)

2021-03-22 Thread Denis Ovsienko via tcpdump-workers
--- Begin Message --- On Mon, 22 Mar 2021 19:00:31 +0100 Harald Welte wrote: > Dear Denis, > > On Sun, Mar 21, 2021 at 11:08:44PM +0000, Denis Ovsienko via > tcpdump-workers wrote: > > Thank you for the offer. For the operating systems specifics please > >

Re: [tcpdump-workers] ARM build slaves (tcpdump mirror in Germany)

2021-03-23 Thread Denis Ovsienko via tcpdump-workers
--- Begin Message --- On Wed, 24 Mar 2021 00:52:00 +0100 Harald Welte wrote: > Hi Denis, > > On Tue, Mar 23, 2021 at 12:35:06AM +0000, Denis Ovsienko via > tcpdump-workers wrote: > > That's great, three worker types are ready to go anytime soon, just > > decide which

[tcpdump-workers] CI status update

2021-04-05 Thread Denis Ovsienko via tcpdump-workers
--- Begin Message --- Hello list. I hope you have a great day. Please find below a brief overview of some current continuous integration matters. The Linux/s390x problem space is now covered with the IBM Z CI service provided by Oregon State University Open Source Lab. It uses Jenkins and is not

Re: [tcpdump-workers] tcpdump mirror in Germany

2021-03-21 Thread Denis Ovsienko via tcpdump-workers
--- Begin Message --- On Sun, 21 Mar 2021 22:04:29 +0100 Harald Welte via tcpdump-workers wrote: > My company sysmocom is running build and test infrastructure for > osmocom.org, and we'd be more than happy to host those ARM build > slaves in Germany. We also operate a number of rpi4 for jenkins

Re: [tcpdump-workers] tcpdump mirror in Germany

2021-03-20 Thread Denis Ovsienko via tcpdump-workers
--- Begin Message --- On Sat, 20 Mar 2021 18:34:34 +0100 Jan Prunk via tcpdump-workers wrote: > Hello, > > I am offering to provide tcpdump mirror in Germany. Are you > interested? Thank you for the offer, but a mirror would not solve any existing problem. Would you like to host any of the

Re: [tcpdump-workers] continuous integration status update

2021-03-03 Thread Denis Ovsienko via tcpdump-workers
--- Begin Message --- On Fri, 12 Feb 2021 16:18:10 + Denis Ovsienko via tcpdump-workers wrote: [...] > The Travis CI subscription will cease in early March (unless there is > a sponsor willing to pay 82.80 USD per month). At this time the > impact of that would be the following: >

Re: [tcpdump-workers] continuous integration status update

2021-03-04 Thread Denis Ovsienko via tcpdump-workers
--- Begin Message --- On Thu, 4 Mar 2021 00:42:23 -0800 Guy Harris wrote: > On Mar 3, 2021, at 2:30 PM, Denis Ovsienko via tcpdump-workers > wrote: > > > A partial replacement for that service is ci.tcpdump.org, which is a > > buildbot instance doing Linux AArch64 buil

[tcpdump-workers] continuous integration status update

2021-02-12 Thread Denis Ovsienko via tcpdump-workers
--- Begin Message --- Hello list. The tcpdump group repositories used to rely mainly on travis-ci.org for free continuous integration. For many years Travis CI GmbH had been making an outstanding contribution to the worldwide open source community, so let's thank all the people who at the time

[tcpdump-workers] assorted build issues

2021-08-15 Thread Denis Ovsienko via tcpdump-workers
--- Begin Message --- Hello list. I hope this finds you well. To follow up on the earlier point about the build problem space mapping, below are a few issues that don't fail building and testing, but might mean potential problems: * Builds that use Autoconf 2.71 generate quite a number of

Re: [tcpdump-workers] [tcpdump] Finding inconsistent outputs of tcpdump with different compilers

2021-08-15 Thread Denis Ovsienko via tcpdump-workers
--- Begin Message --- On Mon, 9 Aug 2021 16:27:27 +0200 Francois-Xavier Le Bail via tcpdump-workers wrote: > cmp $TMPDIR/out1 $TMPDIR/out2 >/dev/null > [ $? = 1 ] && echo "$p" && diff $TMPDIR/out1 $TMPDIR/out2 && > echo Differential analysis is indeed a good solution when the

[tcpdump-workers] CI news September 2021 (RISC-V, illumos)

2021-09-15 Thread Denis Ovsienko via tcpdump-workers
--- Begin Message --- Hello list. This is a semi-periodic summary of recent developments in the continuous integration space of the tcpdump group. It took a few months since Francois-Xavier Le Bail discovered this opportunity, but finally the Buildbot setup includes a hardware RISC-V worker,

Re: [tcpdump-workers] build failures on Solaris

2021-08-02 Thread Denis Ovsienko via tcpdump-workers
--- Begin Message --- On Mon, 2 Aug 2021 14:31:18 -0700 Guy Harris wrote: > solaris11$ /usr/bin/pcap-config --libs > -L/usr/lib -lpcap > solaris11$ /usr/bin/amd64/pcap-config --libs > -L/usr/lib/amd64 -R/usr/lib/amd64 -lpcap > > on my x86-64 Solaris 11 VM. $ uname -a

Re: [tcpdump-workers] build failures on Solaris

2021-08-08 Thread Denis Ovsienko via tcpdump-workers
--- Begin Message --- On Sun, 8 Aug 2021 12:02:53 -0700 Guy Harris wrote: [...] > I've checked in a change to explicitly tell CMake "this is a C-only > project, don't check for a C++ compiler", so it should now think it's > building 64-bit when building with GCC. > > See whether that fixes

[tcpdump-workers] CI news July-August 2021

2021-08-05 Thread Denis Ovsienko via tcpdump-workers
--- Begin Message --- Hello list. Besides the matters recently discussed on the list, a few notable developments in The Tcpdump Group CI took place since the previous update: * Another MIPS worker has been doing builds in the pool for a month. It runs a snapshot of NetBSD-current. Although

Re: [tcpdump-workers] build failures on Solaris

2021-08-08 Thread Denis Ovsienko via tcpdump-workers
--- Begin Message --- On Sun, 8 Aug 2021 01:22:09 -0700 Guy Harris wrote: [...] > I've checked in changes to: > > check the bit-width of the build in autotools; > > on Solaris, use the results of the bit-width checks for > autotools and CMake to figure out which version of

Re: [tcpdump-workers] build failures on Solaris

2021-07-31 Thread Denis Ovsienko via tcpdump-workers
--- Begin Message --- On Sat, 31 Jul 2021 14:55:32 -0700 Guy Harris wrote: [...] > What version of CMake is being used, and how was it installed? > > My Solaris 11 x86-64 virtual machine has CMake 2.8.6 in > /usr/ccs/bin/cmake, installed from Sun^WOracle's Image Packaging > System repositories,

[tcpdump-workers] build failures on Solaris

2021-07-31 Thread Denis Ovsienko via tcpdump-workers
--- Begin Message --- On Sat, 24 Jul 2021 00:11:27 +0100 Denis Ovsienko via tcpdump-workers wrote: > There are more related corner cases of varying severity, > some of which I might have time to describe later. So, as promised... Several warnings are now documented in the build scripts

Re: [tcpdump-workers] build failures on Solaris

2021-08-01 Thread Denis Ovsienko via tcpdump-workers
--- Begin Message --- On Sun, 1 Aug 2021 15:45:39 -0700 Guy Harris wrote: [...] > So where do the Solaris 11 hosts show up on the buildbot site? They don't. Solaris 9 and 11 are not in any CI at all. OpenCSW Buildbot runs on Solaris 10, but uses a single build script. I used OpenCSW shell

Re: [tcpdump-workers] NetBSD breakage

2021-08-11 Thread Denis Ovsienko via tcpdump-workers
--- Begin Message --- On Wed, 11 Aug 2021 15:38:34 -0700 Guy Harris wrote: > I've checked in a change to remove the include of grammar.h from > gencode.c; it builds without problems on macOS, and I suspect it will > build without problems everywhere Thank you, NetBSD has recovered now. I am

[tcpdump-workers] NetBSD breakage

2021-08-11 Thread Denis Ovsienko via tcpdump-workers
--- Begin Message --- Hello list. I have spent some time looking into tcpdump NetBSD builds, which all have failed as a consequence of my libpcap commit 0c21cb27, which had broken the workaround earlier introduced in libpcap commit bb02779. As Guy has noted in a comment just now, the matter

Re: [tcpdump-workers] [libpcap] Keep Win32/Prj/* files ?

2021-12-06 Thread Denis Ovsienko via tcpdump-workers
--- Begin Message --- On Mon, 29 Nov 2021 19:20:32 +0100 Francois-Xavier Le Bail via tcpdump-workers wrote: > Hello, > > The information on building libpcap on Windows with Visual Studio is > here: > https://github.com/the-tcpdump-group/libpcap/blob/master/doc/README.Win32.md > (The supported

Re: [tcpdump-workers] [libpcap] Keep Win32/Prj/* files ?

2021-12-06 Thread Denis Ovsienko via tcpdump-workers
--- Begin Message --- On Mon, 6 Dec 2021 12:31:33 -0800 Guy Harris wrote: [...] > The CMake files are likely to be better maintained than the "use > Visual Studio directly" files, as you don't need Visual Studio, and > don't need to know how Visual Studio solution or project files work >

Re: [tcpdump-workers] pcap_datalink_ex() in linktypes.html

2021-12-18 Thread Denis Ovsienko via tcpdump-workers
--- Begin Message --- On Wed, 8 Dec 2021 23:02:58 + Denis Ovsienko via tcpdump-workers wrote: > I am going to merge the short Markdown file into the long HTML > page at some later point Alright, libpcap/doc/DLT_ALLOCATE_HOWTO.md has been merged into tcpdump-htdocs/linktypes.html

[tcpdump-workers] pcap_datalink_ex() in linktypes.html

2021-11-28 Thread Denis Ovsienko via tcpdump-workers
--- Begin Message --- Hello all. Whilst updating some markup in linktypes.html, I wanted to change the reference to pcap_datalink_ex() into a hyperlink to respective man page, but it turned out there is no such function in libpcap in the first place. There is pcap_datalink_ext(), which has been

[tcpdump-workers] project news November 2021

2021-11-05 Thread Denis Ovsienko via tcpdump-workers
--- Begin Message --- Hello list. I hope this finds you well. Below you can find an overview of assorted recent developments. The read-only git mirror service has moved from bpf.tcpdump.org to git.tcpdump.org. The latter works both as a browsable web-site and as a git clone URL (either https://

[tcpdump-workers] VLAN/MPLS FAQ

2021-11-30 Thread Denis Ovsienko via tcpdump-workers
--- Begin Message --- Hello list. Whilst looking through tcpdump and libpcap issues, I noted that the specifics of "vlan" and "mpls" keywords in pcap filters is one of the most common causes of confusion. So it should be in the FAQ. That said, it is not clear if it would be better to have one

Re: [tcpdump-workers] pcap_datalink_ex() in linktypes.html

2021-12-08 Thread Denis Ovsienko via tcpdump-workers
--- Begin Message --- On Sun, 28 Nov 2021 21:11:27 + Denis Ovsienko via tcpdump-workers wrote: > Hello all. > > Whilst updating some markup in linktypes.html, I wanted to change the [...] On a related note, it does not look right that linktypes.html in the middle of the explanati

[tcpdump-workers] compiler warnings on AIX and Solaris

2021-07-23 Thread Denis Ovsienko via tcpdump-workers
--- Begin Message --- Hello list. As it turns out, on Solaris 9 it is impossible to compile current tcpdump with CFLAGS=-Werror because missing/getopt_long.c yields a few warnings (attached). As far as the current revisions of this file go in FreeBSD, NetBSD and OpenBSD, FreeBSD seems to be the

Re: [tcpdump-workers] compiler warnings on AIX and Solaris

2021-07-24 Thread Denis Ovsienko via tcpdump-workers
--- Begin Message --- [...] > So the only way to fix this is to turn off the warnings; change > 39f09d68ce7ebe9e229c9bf5209bfc30a8f51064 adds macros to disable and > re-enable -Wcast-qual and wraps the offending code in getopt_long.c > with those macros, so the problem should be fixed on Solaris

Re: [tcpdump-workers] compiler warnings on AIX and Solaris

2021-07-25 Thread Denis Ovsienko via tcpdump-workers
--- Begin Message --- On Sat, 24 Jul 2021 10:55:19 -0700 Guy Harris wrote: [...] > If there's a way to force XL C to treat it as a hard error, we need > to update the AC_LBL_CHECK_UNKNOWN_WARNING_OPTION_ERROR autoconf > macro to set the compiler up to use it when testing whether compiler >

Re: [tcpdump-workers] Request for new LINKTYPE/DLT ZBOSS_NCP

2022-01-09 Thread Denis Ovsienko via tcpdump-workers
--- Begin Message --- On Tue, 2 Nov 2021 09:46:30 +0300 Eugene Exarevsky via tcpdump-workers wrote: > Hi all, > > Please, allocate a new LINKTYPE/DLT called ZBOSS_NCP. > > The background is following: we (DSR) are developing Zigbee protocol > stack ZBOSS ( > The stack has serial commands

[tcpdump-workers] project news January 2022

2022-01-13 Thread Denis Ovsienko via tcpdump-workers
--- Begin Message --- Hello list. I almost typed "2021" into the subject of this e-mail, as 2022 still feels futuristic, yet it is here. Today is exactly 31 years from the first public release of tcpdump (2.0 by LBL), which at the time was still the same program as libpcap. As you can see on the

[tcpdump-workers] WinPcap CI

2022-02-02 Thread Denis Ovsienko via tcpdump-workers
--- Begin Message --- Hello list. www.winpcap.org has been down for a couple days, which is breaking libpcap CI in Appveyor. Now that Npcap is the recommended SDK, would it be a good occasion to stop doing CI with WinPcap? -- Denis Ovsienko --- End Message ---

Re: [tcpdump-workers] Selectively suppressing CI on some sites for a commit?

2022-01-07 Thread Denis Ovsienko via tcpdump-workers
--- Begin Message --- On Thu, 6 Jan 2022 23:35:30 -0800 Guy Harris wrote: [...] > It appears that a "GitHub skip hook" may have been first introduce in > Buildbot 0.9.11: > > https://docs.buildbot.net/0.9.11/relnotes/index.html > > with the hook being configurable by a regex match. The

Re: [tcpdump-workers] Selectively suppressing CI on some sites for a commit?

2022-01-06 Thread Denis Ovsienko via tcpdump-workers
--- Begin Message --- On Thu, 6 Jan 2022 14:11:54 -0800 Guy Harris via tcpdump-workers wrote: > I've just updated the libpcap .appveyor.yml to get Npcap from > npcap.com (the Npcap site has been moved there); I added [skip > cirrus] to skip Cirrus CI for that change, and it appears to work.

[tcpdump-workers] endianness of portable BPF bytecode

2022-06-02 Thread Denis Ovsienko via tcpdump-workers
--- Begin Message --- Hello list. In the usual workflow a correct BPF expression eventually compiles to a series of BPF instructions, each of which is a 64-bit structure encoding the (opcode, jt, jf, k) tuple. So long as the compiled bytecode appears only between the OS kernel and libpcap, its

Re: [tcpdump-workers] NetBSD breakage

2022-06-21 Thread Denis Ovsienko via tcpdump-workers
--- Begin Message --- On Thu, 12 Aug 2021 01:18:45 +0100 Denis Ovsienko via tcpdump-workers wrote: > On Wed, 11 Aug 2021 15:38:34 -0700 > Guy Harris wrote: > > > I've checked in a change to remove the include of grammar.h from > > gencode.c; it builds without problems on

Re: [tcpdump-workers] endianness of portable BPF bytecode (DRAFT revision 3)

2022-06-25 Thread Denis Ovsienko via tcpdump-workers
--- Begin Message --- Hello list. Below you can find the next draft revision. It incorporates some feedback received from Guy and Michael, also it reorders the TLVs and adds SnapLen TLV, Netmask TLV and EOF TLV. Also the text has been converted to a man page, so it could live next to

Re: [tcpdump-workers] What's the correct new API to request pcap_linux to not open an eventfd

2022-07-05 Thread Denis Ovsienko via tcpdump-workers
--- Begin Message --- On Fri, 1 Jul 2022 13:55:30 -0400 Bill Fenner via tcpdump-workers wrote: > If we set > pcap_nonblock after pcap_create and before pcap_activate, we get -3 - > which I don't get at all, unless, -3 means "you didn't activate the > pcap yet". My naive reading of the Linux

[tcpdump-workers] NetBSD CI breakage

2022-07-10 Thread Denis Ovsienko via tcpdump-workers
--- Begin Message --- Hello all. The last CI build of the libpcap-1.10 branch failed on netbsd-aarch64 because the latter now uses GCC 12. Commit 4e7f6e8 makes a lazy fix for that in the master branch; if a more sophisticated solution is not required, a simple cherry-pick into libpcap-1.10

Re: [tcpdump-workers] endianness of portable BPF bytecode (DRAFT revision 4)

2022-06-30 Thread Denis Ovsienko via tcpdump-workers
--- Begin Message --- Hello list. Below is revision 4 of the document, unless anyone objects it will be committed to libpcap repository soonish, this way any remaining improvements can be made there when and as necessary. Changes from the previous revision are as follows: * fixup letter case *

[tcpdump-workers] BPF Exam

2022-06-05 Thread Denis Ovsienko via tcpdump-workers
--- Begin Message --- Hello list. A while ago I tried to comprehend a few BPF-related bug reports in libpcap and found it difficult to follow the logic of filter compilation and optimization. On one hand, there is the universally available, but basic "tcpdump -d" pseudocode listing. On the

Re: [tcpdump-workers] endianness of portable BPF bytecode

2022-06-11 Thread Denis Ovsienko via tcpdump-workers
--- Begin Message --- On Sat, 11 Jun 2022 10:51:41 -0400 Michael Richardson wrote: > Denis Ovsienko via tcpdump-workers > wrote: > > Below is a draft of such a file format. It addresses the > > following needs: > > * There is a header with a signatu

Re: [tcpdump-workers] pcap_compile_nopcap() not in man pages

2022-06-14 Thread Denis Ovsienko via tcpdump-workers
--- Begin Message --- On Wed, 12 Aug 2020 12:59:35 -0700 Guy Harris wrote: [...] > So, for now, my inclination is to 1) deprecate pcap_compile_nopcap() > (complete with marking it as deprecated, so code that uses it gets a > compile-time warning on compilers where the deprecation macro is >

Re: [tcpdump-workers] endianness of portable BPF bytecode

2022-06-10 Thread Denis Ovsienko via tcpdump-workers
--- Begin Message --- On Thu, 2 Jun 2022 20:58:38 +0100 Denis Ovsienko via tcpdump-workers wrote: > If there is no convention in place yet, I would like to propose > declaring big-endian as the implicit/default byte order, then > particular file format(s) with headers can override that

Re: [tcpdump-workers] endianness of portable BPF bytecode

2022-06-10 Thread Denis Ovsienko via tcpdump-workers
--- Begin Message --- On Fri, 10 Jun 2022 14:26:34 -0700 Guy Harris wrote: > On Jun 10, 2022, at 1:59 PM, Denis Ovsienko via tcpdump-workers > wrote: > > > Below is a draft of such a file format. It addresses the following > > needs: > > * There is a header with

Re: [tcpdump-workers] NetBSD CI breakage

2022-07-14 Thread Denis Ovsienko via tcpdump-workers
--- Begin Message --- On Wed, 13 Jul 2022 23:16:18 -0700 Guy Harris wrote: > I changed it to a slightly different fix. Thank you. The signed device index hinted at some logic error, but I didn't understand if it required a more sophisticated fix. -- Denis Ovsienko --- End Message ---

[tcpdump-workers] CI news January-May

2022-05-05 Thread Denis Ovsienko via tcpdump-workers
--- Begin Message --- Hello list. Below you can find a digest of some works done on the CI infrastructure during past few months. First of all, the illumos-amd64 Buildbot worker has been replaced. It used to be an OpenIndiana VM from a commercial hosting provider. Several months ago the VM

[tcpdump-workers] ARMv7 unaligned access

2022-08-21 Thread Denis Ovsienko via tcpdump-workers
--- Begin Message --- Hello list. Based on some prior online research, I used to think that ARMv7 is a hardware that allows (by default or after simple tweaking) to terminate a userspace process when it tries to perform an unaligned memory access. Which is exactly the behaviour wanted for the CI

Re: [tcpdump-workers] upcoming tcpslice release

2022-10-16 Thread Denis Ovsienko via tcpdump-workers
--- Begin Message --- On Sat, 15 Oct 2022 15:21:42 -0700 Guy Harris wrote: > On Oct 15, 2022, at 8:03 AM, Denis Ovsienko via tcpdump-workers > wrote: > > > As it turns out, on Linux tcpslice currently fails to build with the > > current master branch of libpcap. This re

[tcpdump-workers] tcpslice 1.6

2022-10-20 Thread Denis Ovsienko via tcpdump-workers
--- Begin Message --- Hello list. tcpslice 1.6 has been released with the following change log. Thanks to everyone who contributed! - Call pcap_dump_close() on the output file. - Implement new flags in ./configure: --enable-instrument-functions, --without-libnids, --without-libosipparser2

[tcpdump-workers] CI news September-October 2022

2022-10-30 Thread Denis Ovsienko via tcpdump-workers
--- Begin Message --- Hello list. I hope this finds you well. Below you can find a digest of the CI infrastructure works since the previous update. * OmniOS has seen some improvements to its Clang packages, so illumos-amd64 now uses Clang 15.0 (was 11.1). * netbsd-amd64 has been upgraded

[tcpdump-workers] upcoming tcpslice release

2022-10-13 Thread Denis Ovsienko via tcpdump-workers
--- Begin Message --- Hello list. Unless anyone objects, the next release of tcpslice (1.6) will be made soonish to flush the few buffered minor bugfixes and to take another item off my to-do list. -- Denis Ovsienko --- End Message --- ___

Re: [tcpdump-workers] upcoming tcpslice release

2022-10-15 Thread Denis Ovsienko via tcpdump-workers
--- Begin Message --- As it turns out, on Linux tcpslice currently fails to build with the current master branch of libpcap. This reproduces in all Linux CI builds and also on my Ubuntu 20.04 PC. The root cause seems to be in libpcap via pcap-config: /usr/bin/ld: cannot find -lsystemd clang:

[tcpdump-workers] CI news June-August 2022

2022-08-14 Thread Denis Ovsienko via tcpdump-workers
--- Begin Message --- Hello list. Below you can find a digest of the CI infrastructure works since the previous update. * FreeBSD/AArch64 in release 13.1 notably improved its ability to run as a virtual machine, and freebsd-aarch64 has been migrated to OSU OSL infrastructure. Thanks to

Re: [tcpdump-workers] configure script problem while working on extention

2022-08-14 Thread Denis Ovsienko via tcpdump-workers
--- Begin Message --- On Fri, 12 Aug 2022 16:27:29 +0200 Christian via tcpdump-workers wrote: > Then I opened the tcpdump.zip archive within the libpcap directory. > step into the directory, call ./configure and it build. success! The git clone of libpcap and the git clone of tcpdump are

  1   2   >