Huge thanks to our Platinum Members Endace and LiveAction,
and our Silver Member Veeam, for supporting the Wireshark Foundation and project.

Wireshark-bugs: [Wireshark-bugs] [Bug 5691] New: dumpcap ring buffer file size limitation

Date: Sun, 13 Feb 2011 12:34:01 -0800 (PST)
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=5691

           Summary: dumpcap ring buffer file size limitation
           Product: Wireshark
           Version: unspecified
          Platform: All
        OS/Version: Windows 7
            Status: NEW
          Severity: Major
          Priority: Low
         Component: Extras
        AssignedTo: wireshark-bugs@xxxxxxxxxxxxx
        ReportedBy: canney@xxxxxxxxxxxxxx


Build Information:
Compiled (32-bit) with GLib 2.22.4, with WinPcap (version unknown), with libz
1.2.3, without POSIX capabilities, without libpcre, with SMI 0.4.8, with c-ares
1.7.1, with Lua 5.1, without Python, with GnuTLS 2.8.5, with Gcrypt 1.4.5, with
MIT Kerberos, with GeoIP.

Running on 32-bit Windows 7, build 7600, with WinPcap version 4.1.2 (packet.dll
version 4.1.0.2001), based on libpcap version 1.0 branch 1_0_rel0b (20091008).

Built using Microsoft Visual C++ 9.0 build 30729
--
dumpcap has a ring buffer file size limitation of 2GB.  I would love to see
this increased to something much larger (50-100GB)

$ grep autostop_filesize capture_opts.h 
gboolean has_autostop_filesize; /*< TRUE if maximum capture file size 
gint32 autostop_filesize; /*< Maximum capture file size */ 
$

Since it is a signed 32 bit integer, it will only go up to 2^31 (2GB).

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