Ethereal-dev: Re: [Ethereal-dev] Request for freeing re-assembled frames

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

Date Index Thread Index Other Months All Mailing Lists
Date Prev Date Next Thread Prev Thread Next
From: ronnie sahlberg <ronniesahlberg@xxxxxxxxx>
Date: Fri, 17 Dec 2004 06:30:05 +1100
On Thu, 16 Dec 2004 13:07:13 +0100, LEGO <luis.ontanon@xxxxxxxxx> wrote:

> This approach allows for many other things:
> - using tcpdump to capture, (which especially at high loads is far
> more reliable than tethereal)
> - using mergecap to join the captures of variuos interfaces
> - having more instances of tethereal doing its job (using more
> processors if available)
> 
> But for mate this creates a hole, the new tethereal instance would
> start not knowing anything about sessions already initiated so mate
> would not be able to relate stuff from the old instance.

Yes, but then again in real world captures  there will be a lot of
missing packets anyway
which would cause the same problems.

> 
> Would it be worth telling mate to dump its current state in a temp
> file so that the new instance can load it into memory at the
> successive runs?

I couldnt say   but my gut feeling is that it would be a lot of work
for very little gain.
I.e.  dont think it would be worth it.