--- Begin Message ---
Thank you for explaining in such a great detail.
> It's about either 1) saying "slicing is forbidden" or 2) saying "here's how
> you do slicing".
I would rather not introduce the limitation if not really necessary. The way
you described earlier made sense to me so I am fi
--- Begin Message ---
On Mar 24, 2021, at 12:32 AM, Jan Adam wrote:
>> So, with incl_len equal to {PayloadSize,VarSize} + 54, orig_len would be
>> equal to {original PayloadSize} + 54, so the original payload size would be
>> orig_len - 54.
>>
>> That would allow the original size and the slic
--- Begin Message ---
>> That should also be noted in the specification.
I updated the specification with information about alignment, SrcID, and
PayloadType.
Slicing a captured packet is not supported by our capturing device.
>>>
>>> But some software can slice packets afterwards. Either
--- Begin Message ---
On Mar 22, 2021, at 7:33 AM, Jan Adam wrote:
>> Are they aligned on natural boundaries?
>
> No, it is not aligned but packet. We use #pragma pack(1) for the footer
> structure.
You should probably add that to the page with the structure definition.
>> What do the four f
_
-Ursprüngliche Nachricht-
Von: Guy Harris
Gesendet: Freitag, 19. März 2021 01:20
An: Jan Adam
Cc: tcpdump-workers@lists.tcpdump.org
Betreff: Re: [tcpdump-workers] Link Layer Type Request NETANALYZER_NG
CAUTION: This email originated from o
--- Begin Message ---
On Mar 15, 2021, at 9:04 AM, Jan Adam wrote:
>> Can the variable be anything *other* than a packet of some sort?
>
> There are only the mentioned 5 representations planned for pcap files since
> this is what our capture device may capture into a pcap file. The
> represent
--- Begin Message ---
> Can the variable be anything *other* than a packet of some sort?
There are only the mentioned 5 representations planned for pcap files since
this is what our capture device may capture into a pcap file. The
representation gives at least the ability to extend in the future
--- Begin Message ---
On Mar 12, 2021, at 4:35 AM, Jan Adam wrote:
>> So is "the variable" the same thing as "the payload"?
>
> That is correct. To be more specific the payload is the value/content of the
> variable.
Can the variable be anything *other* than a packet of some sort? The current
am
Cc: tcpdump-workers@lists.tcpdump.org
Betreff: Re: [tcpdump-workers] Link Layer Type Request NETANALYZER_NG
CAUTION: This email originated from outside of the organization. Do not click
links or open attachments unless you recognize the sender and know the content
is safe. Never provide your pass
--- Begin Message ---
On Mar 8, 2021, at 12:07 AM, Jan Adam via tcpdump-workers
wrote:
> We have created a public document on our website You can point to for the
> description.
>
> Here is the link: https://kb.hilscher.com/x/brDJBw
>
> It contains a more detailed description of the fields i
--- Begin Message ---
Hello
We have created a public document on our website You can point to for the
description.
Here is the link: https://kb.hilscher.com/x/brDJBw
It contains a more detailed description of the fields in the footer structure.
It also contains a C – like structure definition
--- Begin Message ---
On Mar 3, 2021, at 8:58 AM, Jan Adam via tcpdump-workers
wrote:
> for our new analysis product netANALYZER NG I would like to request a new
> link-layer type value.
>
> NETANALYZER_NG
>
> The new Link-Layer-Type format is described as following:
>
> Next-generation pack
--- Begin Message ---
Hi,
for our new analysis product netANALYZER NG I would like to request a new
link-layer type value.
NETANALYZER_NG
The new Link-Layer-Type format is described as following:
Next-generation packet structure:
+---+
| Payload |
.
13 matches
Mail list logo
