Ask Your Question

Revision history [back]

click to hide/show revision 1
initial version

Hi all, the solution was very simple. At one end of the trace was taken with a profitap with the "Keep CRC32" option beeing set. It looks like that Wireshark is interpreting the last two Bytes as Cycle, Data Status and Transfer Status. Checking Protocol Preferences >> Assume packets hace FCS did the trick for me, now the Cycle values are matching at both ends. Thanks to all who responded. /stefan-uwe