How do I clear the capture window in Wireshark?

Wireshark

Wireshark Problem Overview


Is there a way to clear the capture window in Wireshark without restarting the capture or re-applying the filter? It's difficult to tell one set of traffic from another without looking very closely at the timestamp.

Wireshark Solutions


Solution 1 - Wireshark

I don't see a way to clear the window, but hitting 'Restart the running live capture' seems to work.

You can therefore clear the window in WireShark by doing one of the following:

  • Clicking on the green shark-fin to the right of the red Stop button
  • Clicking on Capture > Restart
  • Hitting Ctrl-R.

Solution 2 - Wireshark

Possible workaround w/o stopping/restarting capture

Suppose the last packet captured so far is the xth packet. Just apply the filter frame.number>x and everything disappears :)

Solution 3 - Wireshark

Update: F5 button now reassign to refresh interface.

Wireshark 2.02 refresh capture display Ubuntu : Press Close the capture file

Windows : Press the Green fin Restart current capture

Solution 4 - Wireshark

For Mac users, ⌘r for a restart

Solution 5 - Wireshark

There seems to be no way to clear the window. Just hit the refresh button multiple times fast and hit STOP in the end. It will then give a warning: "No packets captured". That's all. After this you can hit the start capture button to record your packets of concern.

If it gives a pop-up asking to save the capture on hitting refresh every-time, just disable that functionality for time being. Uncheck the "Confirm unsaved capture files" field under Preferences.

enter image description here

Attributions

All content for this solution is sourced from the original question on Stackoverflow.

The content on this page is licensed under the Attribution-ShareAlike 4.0 International (CC BY-SA 4.0) license.

Content TypeOriginal AuthorOriginal Content on Stackoverflow
QuestionRyan ShripatView Question on Stackoverflow
Solution 1 - WiresharkRyan ShripatView Answer on Stackoverflow
Solution 2 - WiresharkDarren NgView Answer on Stackoverflow
Solution 3 - WiresharkmootmootView Answer on Stackoverflow
Solution 4 - WiresharkTom HowardView Answer on Stackoverflow
Solution 5 - WiresharkPrateek BhuwaniaView Answer on Stackoverflow