Skip to content
Snippets Groups Projects

ISO/IEC 13818-1 filter broken

    • Closed Issue created by Wireshark GitLab Migration @ws-gitlab-migration

    This issue was migrated from bug 1461 in our old bug tracker.

    Original bug information:

    Reporter: Nigel Hathaway
    Status: RESOLVED FIXED
    Product: Wireshark
    Component: GTK+ UI
    OS: Windows XP
    Platform: x86
    Version: 0.99.5

    Attachments:

    MPEG2fail: Screenshot showing the bug

    To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information

    Child items 0

    • No child items are currently assigned. Use child items to break down this issue into smaller parts.

    Activity

    • Wireshark GitLab Migration
      Wireshark GitLab Migration @ws-gitlab-migration ·
      Author

      :speech_balloon: Nigel Hathaway said:

      Build Information: Version 0.99.5 (SVN Rev 20677)

      Copyright 1998-2007 Gerald Combs <gerald@‍wireshark.org> 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 with GTK+ 2.10.7, with GLib 2.12.7, with WinPcap (version unknown), with libz 1.2.3, with libpcre 6.4, with Net-SNMP 5.4, with ADNS, with Lua 5.1, with GnuTLS 1.6.1, with Gcrypt 1.2.3, with MIT Kerberos, with PortAudio PortAudio V19-devel, with AirPcap.

      Running on Windows XP Service Pack 2, build 2600, with WinPcap version 4.0 (packet.dll version 4.0.0.755), based on libpcap version 0.9.5, without AirPcap.

      Built using Microsoft Visual C++ 6.0 build 8804

      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 am analysing an RTP stream carrying MPEG2 transport stream packets. It's fine if the packet contains payload only, and fine if it contains adaptation field only, but it messes up if there is both adaptation field and payload. It only takes into account the adaptation field, and then somehow thinks that the packet is less than 188 bytes. In any case, regardless of if the TS packet is messed up (which it isn't in my case) it should never think that a TS packet is anything other than 188 bytes long.
    • Wireshark GitLab Migration added oswindows uigtk version0.x labels

      added oswindows uigtk version0.x labels

    • Wireshark GitLab Migration
      Wireshark GitLab Migration @ws-gitlab-migration ·
      Author

      :speech_balloon: Nigel Hathaway said:

      Created attachment 574 Screenshot showing the bug

      You can see that after the packet with adaptation and payload, it thinks the next packet starts in the payload of this one.

    • Wireshark GitLab Migration
      Wireshark GitLab Migration @ws-gitlab-migration ·
      Author

      :speech_balloon: Jaap Keuter said:

      The same is reported in bug #1672 (closed) and bug #1667 (closed). Could you try with 0.99.6?

    • Wireshark GitLab Migration
      Wireshark GitLab Migration @ws-gitlab-migration ·
      Author

      :speech_balloon: Nigel Hathaway said:

      (In reply to comment #2)  
> The same is reported in bug 1672 and bug 1667.  
> Could you try with 0.99.6?  
>  

I've moved on an I'm not working with MPEG2 data at present, so I can't.
    • Wireshark GitLab Migration
      Wireshark GitLab Migration @ws-gitlab-migration ·
      Author

      :speech_balloon: Jaap Keuter said:

      This problem doesn't seem to exist on 0.99.6. Closing all related bug reports due to no further response.

    • Wireshark GitLab Migration closed

      closed

    • Wireshark GitLab Migration mentioned in issue #1672 (closed)

      mentioned in issue #1672 (closed)

    Please register or sign in to reply