Re: [Wireshark-dev] Option to disable Expert Info for issue with frame length

On Jul 24, 2023, at 1:47 AM, CheeHow WEE wrote: > Thanks for explaining a detailed "possible" implementation of the packet > alignment in previous mails. > It's actually performed within the given PCIe based FPGA capture card, hence > the packets are stored in the card's memory (presumably a ri

Re: [Wireshark-dev] Option to disable Expert Info for issue with frame length

We acknowledge and respect the PCAP Capture File Format documentation. Thanks for explaining a detailed "possible" implementation of the packet alignment in previous mails. It's actually perfor

Re: [Wireshark-dev] Option to disable Expert Info for issue with frame length

On Jul 18, 2023, at 8:10 PM, CheeHow WEE via Wireshark-dev wrote: > There's a "padding" added for a 4-bytes aligned PCAP writing API. > - I understood that the latest Wireshark app dev logic such that length > should not be lesser than captured length. > - In highspeed performance (scale of > 1

Re: [Wireshark-dev] Option to disable Expert Info for issue with frame length

On Jul 18, 2023, at 8:10 PM, CheeHow WEE via Wireshark-dev wrote: > There's a "padding" added for a 4-bytes aligned PCAP writing API. > - I understood that the latest Wireshark app dev logic such that length > should not be lesser than captured length. > - In highspeed performance (scale of > 1

Re: [Wireshark-dev] Option to disable Expert Info for issue with frame length

Sorry for my late reply, >From your article, I understand that the *Captured Packet Length* is the *Frame Length/Length on wire/real length* and *Original Packet Length* is the "*Capture Length/captured length*" in the attached picture. My issue is that the capture card in our system always write

Re: [Wireshark-dev] Option to disable Expert Info for issue with frame length

On Mar 29, 2023, at 10:10 AM, Duy Khanh Pham wrote: > From your article, I understand that the Captured Packet Length is the Frame > Length/Length on wire/real length and Original Packet Length is the "Capture > Length/captured length" in the attached picture. > > My issue is that the capture

Re: [Wireshark-dev] Option to disable Expert Info for issue with frame length

On Mar 22, 2023, at 11:40 AM, Duy Khanh Pham via Wireshark-dev wrote: > My case for this request is when doing network data capturing with a capture > card. The capture card always sets the capture length to a multiple of 4 due > to performance requirement. > > As a result, the real length w

[Wireshark-dev] Option to disable Expert Info for issue with frame length

Hi, My case for this request is when doing network data capturing with a capture card. The capture card always sets the capture length to a multiple of 4 due to performance requirement. As a result, the real length will always be less than or equal to the set captured length. After WireShark add