> > The patch in
> >
> > http://www.ethereal.com/lists/ethereal-dev/200502/msg00451.html
> >
> > introduced a protocol-independent filter based on frame numbers.
>
> So is the purpose of this to set the display to show all
> packets in the
> VoIP conversation, regardless of the protocol?
>
> A general mechanism a tap can use, where it can request a "filter"
> operation in which it either
>
> 1) calls a routine that scans through the packets,
> calls back to the
> tap to ask whether the frame should or shouldn't be included
> and, if it
> should be included, dissects the frame to generate the column
> data and
> adds it to the display
>
> or
>
> 2) calls a routine to clear out the "passed_dfilter"
> flag on all
> frames, loops over the frames and calls a routine to set that flag on
> frames it wants in the display, and then calls another routine that
> scans over all the frames and puts the ones with that flag
> set into the
> display
>
> would probably be the best way to handle this.
>
The objective is to create a string in the display filter window, so that, e.g.,
afterwards another call can be added to the filter. A routine that
shows the packets without building a display filter would not serve that
purpose.
Regards,
Francisco
