Wireshark-bugs: [Wireshark-bugs] [Bug 6767] New: packet-rtc.c incorrect logic for heading extens

Date: Wed, 25 Jan 2012 10:48:05 -0800 (PST)
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=6767

           Summary: packet-rtc.c incorrect logic for heading extension
           Product: Wireshark
           Version: 1.7.x (Experimental)
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: Minor
          Priority: Low
         Component: Wireshark
        AssignedTo: bugzilla-admin@xxxxxxxxxxxxx
        ReportedBy: daniel.ctr.lovelace@xxxxxxx


Build Information:
Version 1.7.1 (SVN Rev 40714 from /trunk)

Copyright 1998-2012 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 (32-bit) with GTK+ 2.22.1, with Cairo 1.10.2, with Pango 1.28.3, with
GLib 2.26.1, with WinPcap (version unknown), with libz 1.2.5, without POSIX
capabilities, with SMI 0.4.8, with c-ares 1.7.1, with Lua 5.1, without Python,
with GnuTLS 2.10.3, with Gcrypt 1.4.6, with MIT Kerberos, with GeoIP, with
PortAudio V19-devel (built Jan 25 2012), with AirPcap.

Running on 32-bit Windows Vista Service Pack 2, build 6002, with WinPcap
version
4.1.2 (packet.dll version 4.1.0.2001), based on libpcap version 1.0 branch
1_0_rel0b (20091008), GnuTLS 2.10.3, Gcrypt 1.4.6, without AirPcap.

Built using Microsoft Visual C++ 10.0 build 40219

Wireshark is Open Source Software released under the GNU General Public
License.

Check the man page and http://www.wireshark.org for more information.
--
I'm writing a subdissector for RTP packets. It essentially decodes header
extensions. The code that calls
dissector_try_string(rtp_hdr_ext_dissector_table, ... requires
rtp_info->info_payload_type_str not to be null. However, info_payload_type_str
is only assigned if the payload type is between 95 and 128.

Why does the header extension depend on payload type? Header extensions could
exist without being in the dynamic payload range.

-- 
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.