TCPDump
4 min
broadcaster can capture the network traffic of a connected input or output for troubleshooting start or stop a capture from the input/output actions menu → tcpdump start/stop while a capture is running, the stream's status indicator shows a recording icon also see start tcp dump on input docid\ dlehjwlm5ogrgfttvtmjo start tcp dump on output docid 68vjl9u4 bjkp1vpobz0e requirements linux capture uses the zdump utility included in the broadcaster installation directory windows capture uses wireshark , which must be installed on the system limitations capture is available only on connected inputs/outputs with a network socket; it is not offered for internal stream types (mux, demux, asi, failover groups, etc ) tcpdump files location capture files are written under the broadcaster files folder \<files folder>/tcpdump/\<input or output id>/capture\<timestamp> pcap files rotate according to the size/count settings, and a tcpdump log in the same folder records any capture utility errors settings tcpdump settings fields max output files (default 10) control file rotation max output file size (kb) (default 1 gb) capture automatically stops when the maximum file size is reached max seconds (default 60) capture will stop when this limit is reached (the max filesize limit takes precedence over this setting) max packet size the maximum number of bytes saved per packet (snap length) the default, 0 , captures full packets and is recommended for most cases set a small value (e g , 128) to capture headers only and reduce file size, or a value at or above your mtu (e g , 1514) to explicitly guarantee full frames
