Wireshark · Ethereal-dev: [ethereal-dev] per frame data / conversations

[Frank Singleton <frank.singleton@xxxxxxxxxxxx>]

Hello,

Thanks for you previous answers about conversations
and dynamic ports.

I have about 7 dissectors, all tvbuffed, and was
going to implement conversation for 2 of them that
can use dynamic port assigment.

I was reading throught the "bxxp" example
and saw comments like 

<snip>
  /* If we have per frame data, use that, else, we must be on the first 
   * pass, so we figure it out on the first pass.
   * 
   * Since we can't stash info away in a conversation (as they are 
   * removed during a filter operation, and we can't rely on the visited
   * flag, as that is set to 0 during a filter, we must save per-frame
   * data for each frame. However, we only need it for requests.
Responses
   * are easy to manage.
   */
</snip>

I generally capture all, then run dispaly filters , or sometimes
I use display filters while capturing.

Can I still do this if I implement conversations, according to the
above comments. Or is there something else more applicable.

Any pointers on using per-frame data ??

Thanks / Frank..


-- 
EUS/SV/Z Frank Singleton      ASO Americas BSS
Office : +1 972 583 3251      ECN 800 33251  
Pager  : +1 800 651 1184      Email : eusfrsi@xxxxxxxxxxxxxxx 
Amateur Radio: VK3FCS/KM5WS   Email : frank.singleton@xxxxxxxxxxxx

Hardware: HP Omnibook 4150 running Redhat Linux 6.2 (2.2.16 kernel).