If those packets show up in the RTP analysis, then they are obviously are accepted at that level, so no worries in my opinion.
Regards, Martin
MartinVisser99@xxxxxxxxx
On Tue, Jun 1, 2010 at 10:31 PM, capricorn 80
<cool_capricorn80@xxxxxxxxxxx> wrote:
Thanks Martin. So i should not be worry in case of RTP calculation.
Regards,
Date: Tue, 1 Jun 2010 21:31:40 +1000
From:
martinvisser99@xxxxxxxxx
To:
wireshark-users@xxxxxxxxxxxxxSubject: Re: [Wireshark-users] IP Error (Header Checksum) can effect Jitter calculation ?
The most likely cause of checksum "errors" when capturing packets with Wireshark is the driver/NIC combination of the machine you are doing this with. Many NICs are able to offload this function from the main CPU, improving performance. The normal network driver knows to ignore the checksum, not doing the work, and assumes it is being handled correctly by the NIC. Wireshark however calculates the checksum by default and matches it with what is in the packet, reporting the error falsely. It is unlikely you will receive real errors with Wireshark, as the CRC32 checks by the NIC and switch will drop errored packets and you won't see them. So you are best off turning this feature off in the appropriate preferences section for each protocol.
See
http://www.wireshark.org/docs/wsug_html_chunked/ChAdvChecksums.html for more details.
Regards, Martin
MartinVisser99@xxxxxxxxx
Hotmail: Powerful Free email with security by Microsoft.
Get it now.
___________________________________________________________________________
Sent via: Wireshark-users mailing list <wireshark-users@xxxxxxxxxxxxx>
Archives: http://www.wireshark.org/lists/wireshark-users
Unsubscribe: https://wireshark.org/mailman/options/wireshark-users
mailto:wireshark-users-request@xxxxxxxxxxxxx?subject=unsubscribe