Comment # 5
on bug 8585
from Jakub Zawadzki
(In reply to comment #4)
> (In reply to comment #3)
> > I could push changes to libpcap, but I don't want to make it more bloated :-)
>
> Why is bloating Wireshark or dumpcap better than bloating libpcap?
I think the idea behind this bug is to create some generic interface and to not
bloat wireshark nor dumpcap.
> Bloating libpcap has the advantage that people don't have to have Wireshark
> in order to capture the DVB information you're trying to capture;
Just to name it, I want to capture MPEG packets[1] (aka DLT_MPEG_2_TS).
> people can write other analyzers without having to write their
> own low-level capturing code.
I'm fine with pushing it to libpcap, I'm also fine to release it under BSD
license.
Still libpcap don't have any API to set some specific options (nor list all
options for UI). AFAIR it was lastly discussed in 2012 ([tcpdump-workers]
Initializing a device). I don't need it right now, but setting frequency from
some window (and not from tzap) would be great.
Looking at sharkfest presentation from comment #2 they have it.
[1] http://en.wikipedia.org/wiki/MPEG_transport_stream#Packet
You are receiving this mail because:
- You are watching all bug changes.
