ANNOUNCEMENT: Live Wireshark University & Allegro Packets online APAC Wireshark Training Session
April 17th, 2024 | 14:30-16:00 SGT (UTC+8) | Online

Wireshark-bugs: [Wireshark-bugs] [Bug 5654] dissector for DVB-CI (Common Interface)

Date: Mon, 7 Feb 2011 07:38:01 -0800 (PST)
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=5654

--- Comment #2 from Bill Meier <wmeier@xxxxxxxxxxx> 2011-02-07 10:37:53 EST ---
Interesting protocol & approach.

I see that this dissector is coded to dissect
DVBCI bytes received as the payload of UDP
(in a manner somewhat similar to that used by packet-gsmtap).

I also see that there's a program (not part of this patch)
which is used to read a log file containing DVBCI bytes
and send them out to the local loopback interface as the
payload of UDP on port 50221.

I'm wondering if an alternative approach wherein the DVBCI
bytes are stored in (say) a pcap format file
(with a special "DVBCI DLT") should be considered.

(A conversion to pcap format can be done quite easily with text2pcap).

(With this approach, only the actual DVBCI bytes would be
dissected/displayed (without the dummy Ethernet/IP/UDP layers)).

(I think that this is the general approach used by packet-radiotap)

Before discussing further, it would be helpful to know a bit
more about how the DVBCI bytes are actually captured.

Are there different solutions ? (different vendors, etc ?)
Is additional information available ? (e.g., timestamps ?)
Is there a (potential) need for "real-time" tapping (as
I understand packet-gsmtap provides) ?
...

(Also: I expect other [core] developers may have thoughts on approaches to
getting DVBCI data into Wireshark).

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