Re: [Wireshark-users] termshark: a terminal UI for tshark

2019-04-23 Thread Peter Wu
(+cc wireshark-dev since some may find this interesting.) Hi Graham, This looks neat, I have added it to the wiki: https://wiki.wireshark.org/Tools Are you aware of sharkd? For interactive use it might be a more suitable backend than tshark. sharkd is part of Wireshark and was developed by Jakub

Re: [Wireshark-users] Question on measuring on both sides of a masquerading server.

2019-04-23 Thread L A Walsh
On 4/23/2019 12:32 PM, Sake Blok | SYN-bit wrote: > > Please note that RTT calculations are done from the view of the capture > point. So if you capture near system A, the roundtrip times for traffic being > sent from A to B will be showing the 'real' roundtrip times, as the data > packets are s

Re: [Wireshark-users] Question on measuring on both sides of a masquerading server.

2019-04-23 Thread Sake Blok | SYN-bit
> On 23 Apr 2019 (Tue), at 19:42, L A Walsh wrote: > > How might I see or measure the rtt time of the remote->MasqServ?. I > don't suppose it would be possible to have the the return-trip times, > both to the MasqServ and to the client added together to see a total? Please note that RTT calcula

[Wireshark-users] Question on measuring on both sides of a masquerading server.

2019-04-23 Thread L A Walsh
I have been trying to trace a performance problem from my desktop client to a remote server, that locally goes through a linux-server running in a masquerade mode. Usually, timings between the local server (doing the masquerade) using *ping* have: rtt min/avg/max/mdev = 0.064/0.136/0.615/0.053 ms,

Re: [Wireshark-users] termshark: a terminal UI for tshark

2019-04-23 Thread M Holt
Just installed and played around for a few minutes -- nice work! On Mon, Apr 22, 2019 at 7:10 PM Graham Clark wrote: > Hi everyone - I thought you might be interested in this spare-time project: > > https://termshark.io > > In my professional life I quite often find myself on a remote machine >