Wireshark-bugs: [Wireshark-bugs] [Bug 7043] Wireshark doesn't calculate the right IPv4 destinati
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=7043
--- Comment #2 from Chris Maynard <christopher.maynard@xxxxxxxxx> 2012-04-09 19:24:56 PDT ---
(In reply to comment #1)
> Fixed in trunk (along with some other option fixes) in r41994. Fixed in
> trunk-1.6 in r41995 and scheduled for 1.6.8. Also scheduled for back-porting
> to 1.4.13.
I should note that with the capture file attached to this bug report, the IP
header checksum is still indicated as invalid by Wireshark, even after the fix.
I assume this is due to IP checksum offload though, as Wireshark also
indicates. If the IP header checksum is incorrect and IP checksum offload is
not the cause, then additional code changes may be required to fix this.
(In reply to comment #0)
> Currently, bad IPv4 options that I know of are internet timestamp with length <
> 5 and basic security with length != 11.
> As far as I know, both of these options should be considered ok according to
> their RFCs, but this is a separate less critical bug.
I also meant to comment on this earlier ... according to my reading of RFC 791,
the basic security length is supposed to be exactly 11 bytes long. Where does
it say otherwise that a length != 11 is OK?
--
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.
