Wireshark · Wireshark-bugs: [Wireshark-bugs] [Bug 10959] Wireshark doesn't parse options after IPv4 MTU Reply option with bad le

Wireshark-bugs: [Wireshark-bugs] [Bug 10959] Wireshark doesn't parse options after IPv4 MTU Repl

Date: Sat, 14 Feb 2015 11:06:15 +0000

What	Removed	Added
CC		[email protected]

Comment # 1 on bug 10959 from Alexis La Goutte

The problem is what the length of the option... 4 or 18.. (i known MTU Length
will be always 4 but when the length is variable, it is complicated...) 
The code prefer stop dissection of IP Option...

You are receiving this mail because:

You are watching all bug changes.

References:
- [Wireshark-bugs] [Bug 10959] New: Wireshark doesn't parse options after IPv4 MTU Reply option with bad length
  - From: bugzilla-daemon

Prev by Date: [Wireshark-bugs] [Bug 10911] Can't open Wireshark (lt-wireshark: Fatal IO error 11 (Resource temporarily unavailable) on X server :55.) - packaged Wireshark works
Next by Date: [Wireshark-bugs] [Bug 10960] DNS LOC data parsed as unknown data
Previous by thread: [Wireshark-bugs] [Bug 10959] New: Wireshark doesn't parse options after IPv4 MTU Reply option with bad length
Next by thread: [Wireshark-bugs] [Bug 10959] Wireshark doesn't parse options after IPv4 MTU Reply option with bad length
Index(es):
- Date
- Thread