| Bug ID |
11370
|
| Summary |
Dumpcap does not understand pcapng
|
| Product |
Wireshark
|
| Version |
Git
|
| Hardware |
x86
|
| OS |
All
|
| Status |
UNCONFIRMED
|
| Severity |
Enhancement
|
| Priority |
Low
|
| Component |
Extras
|
| Assignee |
[email protected]
|
| Reporter |
[email protected]
|
Created attachment 13742 [details]
PcapNG trace with comments
Build Information:
TShark (Wireshark) 1.99.8 (v1.99.1rc0-3542-g2b93f6d from unknown)
Copyright 1998-2015 Gerald Combs <[email protected]> and contributors.
License GPLv2+: GNU GPL version 2 or later
<http://www.gnu.org/licenses/old-licenses/gpl-2.0.html>
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 libpcap, with POSIX capabilities (Linux), without libnl,
with libz 1.2.8, with GLib 2.40.2, with SMI 0.4.8, with c-ares 1.10.0, with Lua
5.2, with GnuTLS 2.12.23, with Gcrypt 1.5.3, with MIT Kerberos, with GeoIP.
Running on Linux 3.13.0-37-generic, with locale de_DE.UTF-8, with libpcap
version 1.5.3, with libz 1.2.8, with GnuTLS 2.12.23, with Gcrypt 1.5.3.
Intel(R) Core(TM) i7-3615QE CPU @ 2.30GHz (with SSE4.2)
Built using gcc 4.8.4.
--
We develop an extcap utility, which needs to send additional data with the
trace engine for dissection. So far, the additional data has been stored as
extra text files, but we would like to add it as comments to the trace.
Comments means using pcapng as a file format.
Dumpcap (and down-the-line tshark/wireshark I guess) does not understand pcapng
and throws an error. Could be also a libpcap issue.
As of right now we provide the utility in two different versions where the
extcap version does deliver plain pcap without comments and a second
stand-alone mode delivers pcapng files.
It would be really nice, if pcapng get's natively supported as a file-format
for capturing, at least for pipes.
You are receiving this mail because:
- You are watching all bug changes.