> On 24 Apr 2019 (Wed), at 00:44, L A Walsh wrote:
> 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 showi
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
> 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
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,
