Wireshark-bugs: [Wireshark-bugs] [Bug 5958] New: RTP stream analysis shows incorrect number of s
Date Index · Thread Index · Other Months · All Mailing Lists
Date Prev · Date Next · Thread Prev · Thread Next
From: bugzilla-daemon@xxxxxxxxxxxxx
Date: Thu, 26 May 2011 06:53:38 -0700 (PDT)
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=5958

           Summary: RTP stream analysis shows incorrect number of sequence
                    errors
           Product: Wireshark
           Version: 1.4.6
          Platform: x86
        OS/Version: Windows XP
            Status: NEW
          Severity: Normal
          Priority: Low
         Component: Wireshark
        AssignedTo: wireshark-bugs@xxxxxxxxxxxxx
        ReportedBy: ser.fejd@xxxxxxxxx


Created an attachment (id=6406)
 --> (https://bugs.wireshark.org/bugzilla/attachment.cgi?id=6406)
Screenshot of analysis

Build Information:
Version 1.4.6 (SVN Rev 36706 from /trunk-1.4)

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 (32-bit) with GTK+ 2.16.6, with GLib 2.22.4, with WinPcap (version
unknown), with libz 1.2.3, 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
Apr
18 2011), with AirPcap.

Running on Windows XP Service Pack 3, build 2600, 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.
--
When analyzing a log from a long RTSP streaming run on a bad network with a lot
of packet loss, it looks as if the sequence error count never recovers after
the sequence number reaches the maximum sequence number and starts over. In the
case shown in the attachment, the reporting of sequence errors looks alright up
until sequence 61. After that, sequence 62 arrives but Wireshark does not
recognize that as the correct sequence number. All packets after that are
tagged with "Wrong sequence nr.", which results in a large sum of sequence
errors.

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