This document describes how to configure the circular/ring buffer feature of Wireshark in order to have enough storage space to run continuous sniffer captures.
There are no specific requirements for this document.
This document is not restricted to specific software and hardware versions.
The information in this document was created from the devices in a specific lab environment. All of the devices used in this document started with a cleared (default) configuration. If your network is live, make sure that you understand the potential impact of any command.
In many troubleshooting scenarios, you must run sniffer captures continuously in order to capture the packets. However, in most of the scenarios, there is not enough storage space for these files. As a workaround, you can configure the circular/ring buffer feature of Wireshark, so that Wireshark overwrites the files based on the file size specified, which consumes less storage space.
In the ring/circular buffer mode, Wireshark writes to several capture files. The file names are based on the number of the file and on the creation date and time. When the first capture file becomes full, Wireshark begins to write to the next file, and so on. This process fills new files until it reaches the number of files specified, at which point the data in the first file is discarded so that a new file can be written.
Ring Buffer Configuration
Complete these steps in order to configure the ring buffer on your device.
- Ensure that the capture port is in the up/down (monitoring) state, and the output rate increments on the interface.
- Navigate to Capture > Options in Wireshark:
- Choose the correct Ethernet interface.
- Name the file, and check the Use multiple files check box.
- Check the Next file every 1 MB or 1 minute check box.
- Check the Ring buffer with < number> of files check box.
- Click Start in order to initiate the packet capture with the circular buffer.
All of the files displayed in the previous image are .pcap files, which can be opened with Wireshark.
This procedure allows you to run a continous sniffer on the device, and store the files on the capture device that runs Wireshark. Then, if you do not need the files, you can delete them, which conserves storage space on the end device.
There is currently no verification procedure available for this configuration.
There is currently no specific troubleshooting information available for this configuration.