[Resend: originally sent to ethereal-dev by mistake]
> Hi,
> Why I get such an odd graphic (tcptrace style) with this capture?
> I'm using 0.10.13
> Cheers,
> Eduardo
What specifically do you think is odd about the tcptrace-style graph for the capture ?
After a bit of work, I found that the tcptrace-style graph looks about as I think it should for the
ftp-data tcp connection in the capture.
(Do note that to see a useful time-sequence graph you must first:
1. filter on a tcp connection;
2. select a frame to determine the data flow for which the sequence numbers are charted.)
The above being said, I did find that I had to do a lot of vertical zooming on the chart to see any
detail.
My guess is that this might be due to the scale used for the vertical axis (sequence numbers):
4,000,000,000 (relative) as the largest number when I did the chart even though there are only
about 10,000,000 bytes in the capture.
I suspect the apparently poor choice is related to the actual starting and ending sequence numbers
in the connection being quite large.
I also note that zooming was very slow.
I'll have a look at the code to see what's going on (since I've also had difficulties with the
vertical scale when I do tcp sequence graphs).
Bill Meier
------- End of forwarded message -------
