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

Ethereal-dev: Re: [Ethereal-dev] large-file support?

Note: This archive is from the project's previous web site, ethereal.com. This list is no longer active.

From: "Naveen Kumar Kaushik" <naveenk@xxxxxxxxxxxxx>
Date: Thu, 24 Jul 2003 11:12:45 +0530
I understand that giving Large file support is not easy.
Some time I face  a particular problem
I have  non zipped larger than 2 GB file  captured by some other tool (ie
Wiretap and zlib limitation does not come in to picture).
Now i  want to open it on window version of ethereal (Window NT,Pentium
II,RAM 128 MB,HDD 20 GB and ethereal-0.9.11)
Following are my observation
1 . For file greater than 5 MB the performance is very bad . It seems to be
problem of window OS . Since same ethereal version on other OS with same
system configuration  (I used FreeBSD) works fine.
2 . For Files in GB it almost hangs

Now By design, all versions of Win32 (Win9x/ME/NT/2000) provide full support
for 64bit pointer file operations , so can we just change source so that for
unzipped file of size greater than 2 GB can be opened on window.ie limited
LFS support.
This can possibly extended to Linux since future kernel releases of linux
might have LFS support (since Linux group is working on it).

Naveen

----- Original Message -----
From: "Guy Harris" <guy@xxxxxxxxxxxx>
To: "Ben Greear" <greearb@xxxxxxxxxxxxxxx>
Cc: <ethereal-dev@xxxxxxxxxxxx>
Sent: Thursday, July 24, 2003 10:39 AM
Subject: Re: [Ethereal-dev] large-file support?


>
> On Wednesday, July 23, 2003, at 10:03 PM, Ben Greear wrote:
>
> > How about making -r -
> > read from standard-input.
>
> That can work, as long as the standard input isn't a pipe, because the
> Wiretap code currently has to be able to seek backward on the file from
> which it's reading (it does that when trying to figure out what type of
> file it's reading) and, in Ethereal, seek forward as well (it has to be
> able to read the data for arbitrary frames, in arbitrary order, from
> the file, because the user could click on frames in random order).
>
> If you're piping to Ethereal or Tethereal, however, that's not going to
> work.
>
> > Then, one could cat large files into ethereal like that.
>
> As long as catting large files into Ethereal doesn't mean piping them
> to Ethereal - unfortunately, that's probably what it *does* mean....\
>
> > Fair enough, I was not sure that seeks would be needed, but if they
> > are, then it becomes more difficult to play with large files.
>
> They most definitely are.  See above.
>
> _______________________________________________
> Ethereal-dev mailing list
> Ethereal-dev@xxxxxxxxxxxx
> http://www.ethereal.com/mailman/listinfo/ethereal-dev
>
>