Wireshark-bugs: [Wireshark-bugs] [Bug 5549] When using ring buffer for continuous capture, popup
Date Index · Thread Index · Other Months · All Mailing Lists
Date Prev · Date Next · Thread Prev · Thread Next
From: bugzilla-daemon@xxxxxxxxxxxxx
Date: Mon, 23 May 2011 07:59:34 -0700 (PDT)
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=5549

Steve Crye <stcrye@xxxxxxxxx> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |stcrye@xxxxxxxxx

--- Comment #2 from Steve Crye <stcrye@xxxxxxxxx> 2011-05-23 07:59:32 PDT ---
(In reply to comment #1)
> Be sure to read the workarounds listed in bug 3046.
> 
> *** This bug has been marked as a duplicate of bug 3046 ***

Thanks,

Please be aware that I had looked at bug 3046 before creating a new bug report
and decided it did not apply in my case.

I never get a hung "Closing File!" dialog, and Wireshark is snoozing along at
about 75% CPU (reported by Sysinternals Process Explorer on XP).

Please help me understand the work-around. My goal is a workable two-stage
filter; 1st stage lipcap "ip proto 0x2f" and the second stage any valid display
filter. I'm not sure how to use dumpcap to accomplish this.

Steve

-- 
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.