diff options
| author | Guy Harris <guy@alum.mit.edu> | 2018-01-08 16:38:10 -0800 |
|---|---|---|
| committer | Guy Harris <guy@alum.mit.edu> | 2018-01-09 00:38:51 +0000 |
| commit | af0f49e80dce20b50ca757b52c2454e137ce1c74 (patch) | |
| tree | f4bdde99005a0d8374ebea72ff76f58b4c30073c /wiretap/visual.c | |
| parent | 94479aded162aecce6289bdf26f95073bed0dc55 (diff) | |
Use pcapng as the name of the file format.
At one point, I remember a discussion resulting in the official name of
the next-generation replacement for pcap format being changed to
"pcapng", with no hyphen.
Make Wireshark reflect that.
Change-Id: Ie66fb13a0fe3a8682143106dab601952e9154e2a
Reviewed-on: https://code.wireshark.org/review/25214
Reviewed-by: Guy Harris <guy@alum.mit.edu>
Diffstat (limited to 'wiretap/visual.c')
| -rw-r--r-- | wiretap/visual.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/wiretap/visual.c b/wiretap/visual.c index 90e607ef52..0c085ec393 100644 --- a/wiretap/visual.c +++ b/wiretap/visual.c @@ -347,7 +347,7 @@ visual_read_packet(wtap *wth, FILE_T fh, struct wtap_pkthdr *phdr, Most Visual capture types include the FCS in the original length value, but don't include the FCS as part of the payload or captured length. This is different from the model used in most other capture - file formats, including pcap and pcap-ng in cases where the FCS isn't + file formats, including pcap and pcapng in cases where the FCS isn't captured (which are the typical cases), and causes the RTP audio payload save to fail since then captured len != orig len. |