Comment # 13
on bug 8629
from Chris Maynard
I don't know enough about TCO and all of its implementations, but if TCO is
enabled, is the TCP checksum that Wireshark sees always 0x0000? I doesn't seem
so, based on the current comment in the Wireshark code. Assuming that it's not
always going to be 0x0000, then I still think it could be useful to provide a
way to allow reassembly to be attempted even if checksums are computed by
Wireshark to be invalid. I don't think that disabling TCO would always be an
option.
I guess we can leave that as a separate enhancement if anyone really sees value
in implementing it ... along with possibly adding tcp.checksum_computed, if
there's value in doing that too. Regarding the latter, if deemed useful, it
might also be useful to add ip.checksum_computed, udp.checksum_computed, ...
You are receiving this mail because:
- You are watching all bug changes.