https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=6965
Summary: dvb-ci dissector: dissect descriptor loops by using
mpeg-descriptor
Product: Wireshark
Version: SVN
Platform: x86
OS/Version: All
Status: NEW
Severity: Enhancement
Priority: Low
Component: Wireshark
AssignedTo: bugzilla-admin@xxxxxxxxxxxxx
ReportedBy: wireshark@xxxxxxxxx
Build Information:
TShark 1.7.1 (SVN Rev 41627 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 (64-bit) with GLib 2.24.2, with libpcap, with libz 1.2.3.4, without
POSIX capabilities, without SMI, without c-ares, without ADNS, without Lua,
without Python, with GnuTLS 2.8.6, with Gcrypt 1.4.5, with MIT Kerberos,
without
GeoIP.
Running on Linux 2.6.32-5-amd64, with locale en_US.UTF-8, with libpcap version
1.1.1, with libz 1.2.3.4.
Built using gcc 4.4.5.
--
Dear all,
I'm happy to see that support for dvb-si descriptors was comitted on Friday
(mpeg2-descriptor).
The DVB-CI descriptor can use this for apdus that contain such descriptors, see
the attached patch.
I call proto_mpeg_descriptor_dissect() directly from dvb-ci. This is working ok
except that mpeg_descr does not show up in frame.protocols (which is ok, a
descriptor is not a new protocol) and mpeg_descr doesn't work as a display
filter.
The components such as mpeg_descr.tag can be filtered without problems.
An alternative to a direct function call would be to use
new_register_dissector("mpeg2_descr", ...) and find_dissector("mpeg2_descr")
Do you have a clear preference for any of the two approaches?
Best regards,
Martin
--
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.
