• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1006
  • Last Modified:

Bad TCP packets Q in Wireshark

how many Bad TCP packets in a single capture is considered as not good?  i.e.; could cause an issue with the specific TCP Stream?

thank you.

  • 2
1 Solution
John HurstBusiness Consultant (Owner)Commented:
If you have lost or bad (corrupted) packets in a stream, you are likely to have a corrupted download. I do not get much (if any) corruption in my TCP/IP streams (and I do a lot of downloads over time).

On the other hand, errot packets are prevalent. See below for a very tiny sample. So long as (a) your communications are normal and (b) you are not suffering any loss, then these error packets are nothing to worry about. I don't think there is a normal level.

The picture below is from CommView, which is a commercial packet sniffer.

... Thinkpads_User
John HurstBusiness Consultant (Owner)Commented:
rastafaray - Any follow up from you on this?  ... Thinkpads_User
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Get your problem seen by more experts

Be seen. Boost your question’s priority for more expert views and faster solutions

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now