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
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
!, um, ignore this comment! :-)
-linda
On 3/28/2019 7:35 AM, L A Walsh wrote:
> I was looking to understand the Round Trip Time graph and why it
>
> seems to jump up and down between near 0 and 270ms. That doesn't make
> sense to me -- first I don't see how some of them would have a
On 3/28/2019 7:35 AM, L A Walsh wrote:
> (Sorry for duplicates if there are any)
> Usually I see a copy of my email come back to me when I send
> an email to a list, but have seen nothing back from the list.
> I verified my list options, and it seems there might be one
> t
(Sorry for duplicates if there are any)
Usually I see a copy of my email come back to me when I send
an email to a list, but have seen nothing back from the list.
I verified my list options, and it seems there might be one
that could cause suppression depending on definintions, so I
toggled
I was looking to understand the Round Trip Time graph and why it
seems to jump up and down between near 0 and 270ms. That doesn't make
sense to me -- first I don't see how some of them would have an
RTT time of near 0 -- I don't see how that would be possible, so
I figure I don't understand how
I was looking to understand the Round Trip Time graph and why it
seems to jump up and down between near 0 and 270ms. That doesn't make
sense to me -- first I don't see how some of them would have an
RTT time of near 0 -- I don't see how that would be possible, so
I figure I don't understand how
