https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=6449
Summary: RTPS2 dissector doesn't handle 0 in the
octestToNextHeader field
Product: Wireshark
Version: 1.6.2
Platform: x86-64
OS/Version: Ubuntu
Status: NEW
Severity: Normal
Priority: Low
Component: Wireshark
AssignedTo: bugzilla-admin@xxxxxxxxxxxxx
ReportedBy: mitza@xxxxxxxxxx
Build Information:
TShark 1.6.2
Copyright 1998-2011 Gerald Combs <gerald@xxxxxxxxxxxxx> and contributors.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
Compiled (64-bit) with GLib 2.24.1, with libpcap 1.0.0, with libz 1.2.3.3,
without POSIX capabilities, without libpcre, without SMI, without c-ares,
without ADNS, without Lua, without Python, with GnuTLS 2.8.5, with Gcrypt
1.4.4,
with MIT Kerberos, without GeoIP.
Running on Linux 2.6.32-34-generic, with libpcap version 1.0.0, with libz
1.2.3.3.
Built using gcc 4.4.3.
--
The field "octetsToNextHeader" (rtps2.sm.octetsToNextHeader) may be zero for
the last submessage in the message (see RTPS spec 2.1 sections 8.3.3.2.3 and
9.4.5.1.3). However when the field is zero, wireshark does not correctly
dissect the submessage, and thinks there is an "unknown" submessage following
it.
--
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.