Ethereal-dev: RE: [ethereal-dev] Visited is zero after a filter operation ...

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

From: Jeff Foster <jfoste@xxxxxxxxxxxx>
Date: Wed, 23 Aug 2000 08:22:52 -0500
I feel your pain.

Can't we treat the secondary passes, to do filters, different and not reset
the visited flag?  This has implications in the conversation coding, they
would only be created during the first pass. It may also impact other parts
of the program, but I leave that discussion to others that know more then
I do. It seems to me that this would speed secondary passes up because some
of the work doesn't have to be done for each pass, only the first pass.

Jeff Foster
jfoste@xxxxxxxxxxxx


> Foiled again.
> 
> I was hoping to build the last bits needed in the smtp decoder around the
> visited flag.
> 
> This is the bit where I can correctly handle the message part of an smtp
> trace.  
> 
> If the packet has been visited, then I will rely on the saved per frame
> state if it exists.
> 
> Unfortunately, visited is reset to zero when you filter, which does not
help.
> 
> So, now I need to keep per packet state for all frames. I had been hoping
> to avoid that.
> 
> 
> Regards
> -------
> Richard Sharpe, sharpe@xxxxxxxxxx