Sent by:
[EMAIL PROTECTED] cc:
reshark.org Subject: Re:
[Wireshark-dev] Add checksum
ntanon"
> <[EMAIL PROTECTED]> To: "Developer support
> list for Wireshark"
> Sent by:
>
> [EMAIL PROTECTED] cc:
> reshark.org Subject: Re:
> [Wire
Sent by:
[EMAIL PROTECTED] cc:
reshark.org Subject: Re:
[Wireshark-dev] Add checksum
On 2/5/07, [EMAIL PROTECTED]
<[EMAIL PROTECTED]> wrote:
> Hello Jeff,
> Thank you for your comments, I will follow your advices and request a new
> DLT for MTP2 with FCS.
> But before, I will, first, ask for the agreement of the board manufacturer.
> I hope they will not disagree..
>
> In the
m> cc:
Sent by: Subject: Re:
[Wireshark-dev] Add checksum validation option for MTP2
[EMAIL PRO
Salut Florent,
[EMAIL PROTECTED] wrote:
> In fact, the FCS checksum are not ahead the sequence numbers, but after the
> payload.
> So the MTP2 header is not changed, we have just two additional bytes
> containing the CRC16.
> I did join somes messages (captured with libpcap) to show the impact o
m> cc:
Sent by: Subject: Re:
[Wireshark-dev] Add checksum validation option for MTP2
[EMAI
[EMAIL PROTECTED] wrote:
> This patch add an option to validate the MTP2 Frame Check Sequence.
> You can activate this option if you are using a capture device on PCM
> links, and if you want to identify malformed Packet, or noise.
> If you are reading rf5 files, you must not activate the check
Hello,
This patch add an option to validate the MTP2 Frame Check Sequence.
You can activate this option if you are using a capture device on PCM
links, and if you want to identify malformed Packet, or noise.
If you are reading rf5 files, you must not activate the checksum
validation, as t
