>> I.e., a diagram like
>> http://www.networkchemistry.com/products/packetyzer/images/ss_
>tcp_trace.gif
>?
Yes, exactly. But there are limitations to what packetyzer can do.
On 02:09 AM 4/7/2005, Francisco Alcoba (TS/EEM) wrote:
>The code is general, it is not tied to VoIP analysis. I am writing a function
>to plot general diagrams that I hope I can get ready in a while. My idea is, rather
>than using it from a specific protocol, calling it from the main window to graph
>the displayed packets. The disadvantage there is that you will have no such a thing
>as a protocol specific context menu option -like "go to the segment this packet is
>acking"-; you will, however, be able to focus the main window on a packet by clicking
>on it, and there you can have those options. You will have also general packet information
>on the graph, not specific for one protocol level.
>
>The main advantage, of course, is that it should be possible to make graphs of
>arbitrary packet combinations. I attach a sample of how it will -I hope- look.
>
>Anyway, using it for something protocol-specific should be quite straightforward -thanks
>to Alejandro-.
Thank you. I think having TCP specific information in the bounce diagram is important. For me, I'm limited to 128bytes of capture anyway. Or the content is encrypted. So doing tcp analysis via the bounce diagram would come in handy.
hsb
