We are facing an issue in our network. To debug this issue when we decided to do a capture using wireshark, the capture shows some frames with "Frame check sequence: 0xa78b22ce [incorrect, should be 0x56e60339]". The wireshark version that this is seen on was 1.0.4. Then I upgraded to the latest version of wireshark, i.e. 1.6.0. And this same trace does not show this FCS incorrect anymore. It only says "Trailer: a78b22ce". So now I am confused if the previous wireshark was actually showing us an FCS error or not? Which wireshark is showing the right information?
This question is marked "community wiki".
asked 18 Jul '11, 02:10
You might need to enable "Assume frames have FCS" in the Ethernet protocol preferences.
BTW (as a personal interest) what NIC / Capture hardware have you used that passes the FCS to Wireshark?
answered 18 Jul '11, 02:23