This is our old Q&A Site. Please post any new questions and answers at

I'm using Wireshark to try and capture some very rare events that occur very infrequently (months between) but Wireshakr shutsdown after a couple of days. It's configured to use ring buffered, multiple trace files, but when I return to the machine after more than 2/3 days Wireshark is not running. There is plenty of RAM and disc space. I've asked other people and get the answer"It just does that" which is not a lot of use to me. Any help would be greatly appeciated. Thanks.

asked 16 Sep '10, 09:14

dorsetsteve's gravatar image

accept rate: 0%

Wireshark keeps state-information and reassembled data in memory. This means that even if you write to several files to disk, the memory use does increase over time. See:

You can use 'dumpcap' to do the capturing instead, I have used dumpcap to capture a rare problem too and it has been running for months. The syntax you could use is:

dumpcap -i interface -w file -b filesize:16384 -b files:1024

which will create 1024 files of 16MB, giving you a 16GB ringbuffer. When the problem occurs, just stop dumpcap and use wireshark (or tshark) to analyse the files.

permanent link

answered 16 Sep '10, 09:48

SYN-bit's gravatar image

SYN-bit ♦♦
accept rate: 20%

Your answer
toggle preview

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here



Answers and Comments

Markdown Basics

  • *italic* or _italic_
  • **bold** or __bold__
  • link:[text]( "title")
  • image?![alt text](/path/img.jpg "title")
  • numbered list: 1. Foo 2. Bar
  • to add a line break simply add two spaces to where you would like the new line to be.
  • basic HTML tags are also supported

Question tags:


question asked: 16 Sep '10, 09:14

question was seen: 1,231 times

last updated: 16 Sep '10, 09:48

p​o​w​e​r​e​d by O​S​Q​A