https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=6996
Summary: Malformed Packets H263-1996 (RFC2190)
Product: Wireshark
Version: 1.6.5
Platform: x86
OS/Version: Windows 7
Status: NEW
Severity: Major
Priority: Low
Component: Wireshark
AssignedTo: bugzilla-admin@xxxxxxxxxxxxx
ReportedBy: 2006.bikash@xxxxxxxxx
Created attachment 8085
--> https://bugs.wireshark.org/bugzilla/attachment.cgi?id=8085
PCAP file for H263-1996
Build Information:
Version 1.6.5 (SVN Rev 40429 from /trunk-1.6)
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 GLib 2.26.1, with WinPcap (version
unknown), with libz 1.2.5, without POSIX capabilities, without libpcre, 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
10 2012), with AirPcap.
Running on 32-bit Windows 7 Service Pack 1, build 7601, 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++ 9.0 build 21022
Wireshark is Open Source Software released under the GNU General Public
License.
Check the man page and http://www.wireshark.org for more information.
--
For H263-1996 (RFC2190) for some RTP packets Wireshark is showing malformed
packets, which is not correct. It is a valid stream. But only when the stream
data length is 2, 3 or 4 bytes it is showing like that. FRom my analysis i have
found that even if padding is true and padding data is there. In the RTP header
it is not showing those fields. I attached the PCAP file for your reference.
--
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.
