On Tue, Nov 13, 2012 at 9:15 PM, Alexander Koeppe <forma...@online.de> wrote: > Am 12.11.2012 11:41, schrieb Cristian Constantin: >> hi! >> >> I am just a bit confused about the way the tcp graphs are presented to >> the user. >> I am using debian/Version 1.6.5 >> >> 1. tcp. if one selects (for example): >> >> Statistics/TCP Stream Graph/Window Scaling Graph >> >> from the main menu, one gets the graph from the perspective of the >> endpoint which is >> represented by source ip address, source ip port of the frame containing >> the tcp segment >> selected in the main wireshark window, right? > > Right. As the source can only tell something about the window available > on it's end in the ACK packages, this selection has being used to graph > the values. It's up to the user choosing the right direction as it has > been done with the other graphs (let along the oposite direction of the > values graphed in the other graphs).
cristian: yes, but my point was that for sctp this is done in a much more intuitive fashion, which imo is more user friendly. > >> for getting the graph for the other endpoint, I have to close the >> current graph and select a tcp >> segment with the source ip/port of the other endpoint and select again: >> >> Statistics/TCP Stream Graph/Window Scaling Graph >> >> wouldn't have been more intuitive and easier to use (from the user >> perspective) changing the >> graph dynamically when another source endpoint is selected in the main >> window? or to present >> such a choice in the tcp graph windows? > > You mean to add a option to the graph control window, fired up in the > background to toggle between the direction? > crisitian: yes, something like that. from what I understand from martin this should be available in newer versions. thanks. bye now! ___________________________________________________________________________ Sent via: Wireshark-dev mailing list <wireshark-dev@wireshark.org> Archives: http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
