[tcpdump-workers] Request for new LINKTYPE_* code LINKTYPE_AUERSWALD_LOG

2021-02-03 Thread developer--- via tcpdump-workers
--- Begin Message ---
Dear tcpdump developers,

We would like to request a dedicated LINKTYPE_* / DLT_* code.
Auerswald is a major German telecommunications equipment manufacturer.
We have implemented the option to capture (combined) network traffic and 
logging information as pcap/pcapng in our soon to be released new product line.

For development, we so far have used LINKTYPE_USER0 and would like to change 
this to a proper code before the commercial release.

We also plan to publicly release the dissector and would like to make sure both 
can be released with a proper code from the get go.
The dissector we currently use is however only in lua.

Our preferred name would be
LINKTYPE_AUERSWALD_LOG

If anyone is interested we can provide further information.

Best regards

Frank Gorgas-Waller
Software Architect

Auerswald Gesellschaft für Datensysteme mbH
Vor den Grashöfen 1
38162 Cremlingen
Germany

Registered at AG Braunschweig HRB 7499
Management board:
Dipl.-Ing. Gerhard Auerswald
Dipl.-Kfm. (FH) Christian Auerswald

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

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

2021-02-03 Thread Francois-Xavier Le Bail via tcpdump-workers
--- Begin Message ---
On 01/02/2021 18:08, Denis Ovsienko via tcpdump-workers wrote:
> 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 requested a renewable OSS allowance on 29 January, got the
> template response and confirmed the details. Let's see where it goes.
> The account is at 3790/1 credits as of today, in other words, three
> more builds of libpcap or at most one tcpdump build, if/when the latter
> migrates.

To save CI runtime, I have committed a063c2d21417345ee583551ef2c07a0be6b32696 
for libpcap.

This will currently run only five builders (amd64, arm64, ppc64le, s390x and 
osx) and do the matrix processing with scripts.

We can build with ~ half the time (Total time ~26 mins).

These scripts can be used locally for build tests, used on other CI and easily 
be updated to run new tests (32 bits builds, sanitizers, coverage, etc).

Next step is doing similar setup for tcpdump...
--- End Message ---
___
tcpdump-workers mailing list
tcpdump-workers@lists.tcpdump.org
https://lists.sandelman.ca/mailman/listinfo/tcpdump-workers

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

2021-02-03 Thread Michael Richardson via tcpdump-workers
--- Begin Message ---
Francois-Xavier Le Bail via tcpdump-workers wrote:
> To save CI runtime, I have committed
> a063c2d21417345ee583551ef2c07a0be6b32696 for libpcap.

> This will currently run only five builders (amd64, arm64, ppc64le,
> s390x and osx) and do the matrix processing with scripts.

Thanks.

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

Re: [tcpdump-workers] Request for new LINKTYPE_* code LINKTYPE_AUERSWALD_LOG

2021-02-03 Thread Guy Harris via tcpdump-workers
--- Begin Message ---
On Feb 3, 2021, at 6:54 AM, developer--- via tcpdump-workers 
 wrote:

> We would like to request a dedicated LINKTYPE_* / DLT_* code.
> Auerswald is a major German telecommunications equipment manufacturer.
> We have implemented the option to capture (combined) network traffic and 
> logging information as pcap/pcapng in our soon to be released new product 
> line.
> 
> For development, we so far have used LINKTYPE_USER0 and would like to change 
> this to a proper code before the commercial release.
> 
> We also plan to publicly release the dissector and would like to make sure 
> both can be released with a proper code from the get go.
> The dissector we currently use is however only in lua.
> 
> Our preferred name would be
> LINKTYPE_AUERSWALD_LOG
> 
> If anyone is interested we can provide further information.

Please provide a detailed description of the packet format, sufficient to allow 
somebody to make a program such as tcpdump, or Wireshark, or anything else that 
reads pcap or pcapng files.
--- End Message ---
___
tcpdump-workers mailing list
tcpdump-workers@lists.tcpdump.org
https://lists.sandelman.ca/mailman/listinfo/tcpdump-workers

Re: [tcpdump-workers] Request for new LINKTYPE_* code LINKTYPE_AUERSWALD_LOG

2021-02-03 Thread Michael Richardson via tcpdump-workers
--- Begin Message ---

developer--- via tcpdump-workers  wrote:
> We would like to request a dedicated LINKTYPE_* / DLT_* code.
> Auerswald is a major German telecommunications equipment manufacturer.
> We have implemented the option to capture (combined) network traffic
> and logging information as pcap/pcapng in our soon to be released new
> product line.

> For development, we so far have used LINKTYPE_USER0 and would like to
> change this to a proper code before the commercial release.

> We also plan to publicly release the dissector and would like to make
> sure both can be released with a proper code from the get go.  The
> dissector we currently use is however only in lua.

> Our preferred name would be LINKTYPE_AUERSWALD_LOG

That sounds great.
Ideally, you would have a document somewhere that would describe your capture
format.  We might want to review the format.

I would note that if you are just adding logging, and you just want to use
pcapng, that you might store your ethernet captures as normal EN10B, and your
logging in a new LINKTYPE_, which was specific to your log format.
In pcapng, you can mix different LINKTYPEs, in a single file.
(But, not in pcap, which is/was a major reason pcapng was designed)

Then you can ideally follow:

  
https://github.com/the-tcpdump-group/libpcap/blob/master/doc/DLT_ALLOCATE_HOWTO.md

send a pull request.

> If anyone is interested we can provide further information.

> Best regards

> Frank Gorgas-Waller Software Architect

> Auerswald Gesellschaft für Datensysteme mbH Vor den Grashöfen 1 38162
> Cremlingen Germany

--
]   Never tell me the odds! | ipv6 mesh networks [
]   Michael Richardson, Sandelman Software Works|IoT architect   [
] m...@sandelman.ca  http://www.sandelman.ca/|   ruby on rails[

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