Just pass on a snapshot length of 0 to the dumper.

It means "snapshot length unknown".

For most file formats, the snapshot length isn't recorded (even for
formats that support slicing - all they record is the on-the-network
length, and length after slicing, for each packet), so it's ignored in
the dumper.

The one exception is pcap, which records it in the file header; if it's
unknown, the pcap-writing code picks the maximum supported snapshot
length for the file's link-layer header type.

Change-Id: Ieda5dfe34c4bac63e43fdadeff31799ac3c908de
Reviewed-on: https://code.wireshark.org/review/30657
Reviewed-by: Guy Harris <guy@alum.mit.edu>

1 files changed, 0 insertions, 6 deletions

diff --git a/tshark.c b/tshark.c
index d378ad72b3..e519387ce1 100644
--- a/tshark.c
+++ b/tshark.c
@@ -3107,12 +3107,6 @@ process_cap_file(capture_file *cf, char *save_file, int out_file_type,
   if (save_file != NULL) {
     /* Set up to write to the capture file. */
     snapshot_length = wtap_snapshot_length(cf->provider.wth);
-    if (snapshot_length == 0) {
-      /* Snapshot length of input file not known. */
-      snapshot_length = WTAP_MAX_PACKET_SIZE_STANDARD;
-    }
-    tshark_debug("tshark: snapshot_length = %d", snapshot_length);
-
     wtap_dump_params_init(&ng_params, cf->provider.wth);
 #ifdef PCAP_NG_DEFAULT
     if (ng_params.idb_inf->interface_data->len > 1) {