Comment # 2
on bug 8629
from Chris Maynard
(In reply to comment #1)
> The current behavior is done on purpose (see revision 17196 for details).
I think you mean r17612, yes?
Was the main intent of that change to still allow reassembly, since the
checksum is *probably* fine in most cases? Maybe we could still allow
reassembly in this case, but still mark the checksum as bad, which it is? If
nothing else, it would probably still be nice for Wireshark to display its
computed checksum, which would be 0xfffe in this case, same as tcpdump.
I'd vote to still allow reassembly, but to mark the checksum as incorrect.
You are receiving this mail because:
- You are watching all bug changes.