For the sake of future reference, I just ran a single capture test,
FWIW, with tcpdump. It was able to write a file size larger than 2Gs
on a 32-bit Debian system.
Shehjar Tikoo wrote:
> I've seen a few posts in wireshark-users archive where Ulf Lamping
> mentions incorporating support for gin
On Wed, Jun 27, 2007 at 01:25:05PM +1000, Shehjar Tikoo wrote:
> >> Can the devs please modify the configure scripts and add these
> >> two flags to enable large file support by default?
> >>
> >> I've tested this on Linux.
> >
> > And this will work with zlib and wireshark enabled as well? If no
Stephen Fisher schrieb:
> On Tue, Jun 26, 2007 at 08:27:03AM +0200, Ulf Lamping wrote:
>
>> You'll need to compile without libz, as libz is (optionally?) used to
>> work with capture files and it will by default use 32 bit file offsets
>> on machines which uses 32 bits for long values. So you
Stephen Fisher wrote:
> Would it be worth the effort to put some code in that would use the zlib
> reading and writing functions for uncompressed/compressed use < 2GB vs.
> normal reading and writing functions for non-compressed files of any
> size based on a user preference?
I don't know how m
Joerg Mayer wrote:
> On Tue, Jun 26, 2007 at 07:23:33PM +1000, Shehjar Tikoo wrote:
>> $ CFLAGS=-D_GNU_SOURCE\ -D_FILE_OFFSET_BITS=64 ./configure
>> --enable-wireshark=no --without-zlib
>
>> Can the devs please modify the configure scripts and add these
>> two flags to enable large file support by
On Tue, Jun 26, 2007 at 08:27:03AM +0200, Ulf Lamping wrote:
> You'll need to compile without libz, as libz is (optionally?) used to
> work with capture files and it will by default use 32 bit file offsets
> on machines which uses 32 bits for long values. So you can compile
> Wireshark/Tshark w
On Tue, Jun 26, 2007 at 07:23:33PM +1000, Shehjar Tikoo wrote:
> $ CFLAGS=-D_GNU_SOURCE\ -D_FILE_OFFSET_BITS=64 ./configure
> --enable-wireshark=no --without-zlib
> Can the devs please modify the configure scripts and add these two flags
> to enable large file support by default?
>
> I've te
Ulf Lamping wrote:
> Shehjar Tikoo schrieb:
>> I've seen a few posts in wireshark-users archive where Ulf Lamping
>> mentions incorporating support for gint64 offsets for traffic dump files.
>>
>> Does this imply that tshark can write pcap files using large file
>> support on Linux without the ne
Shehjar Tikoo schrieb:
> Hi all,
>
> I've seen a few posts in wireshark-users archive where Ulf Lamping
> mentions incorporating support for gint64 offsets for traffic dump files.
>
> Does this imply that tshark can write pcap files using large file
> support on Linux without the need to resort t
Hi all,
I've seen a few posts in wireshark-users archive where Ulf Lamping
mentions incorporating support for gint64 offsets for traffic dump files.
Does this imply that tshark can write pcap files using large file
support on Linux without the need to resort to multiple capture ring
files?
If
10 matches
Mail list logo
