Date: Thu, 25 Nov 1999 17:31:07 -0500 From: Greg Lehey <grog@mojave.sitaranetworks.com> To: "Niels Chr. Bank-Pedersen" <ncbp@bank-pedersen.dk>, freebsd-questions@FreeBSD.ORG Subject: Re: ping response times over ppp Message-ID: <19991125173107.16398@mojave.sitaranetworks.com> In-Reply-To: <19991125230609.A23253@bank-pedersen.dk>; from Niels Chr. Bank-Pedersen on Thu, Nov 25, 1999 at 11:06:09PM %2B0100 References: <19991125230609.A23253@bank-pedersen.dk>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thursday, 25 November 1999 at 23:06:09 +0100, Niels Chr. Bank-Pedersen wrote: > Hi, > > We are doing some testing of some new network equipment, and I've > stumbled across the following: > > 64 bytes from 192.168.10.10: icmp_seq=22 ttl=253 time=210.361 ms > 64 bytes from 192.168.10.10: icmp_seq=23 ttl=253 time=210.392 ms > > All responsetimes equals n*10 + epsilon [ms]. I'm pretty sure we don't have > any queuing involved that could influence the results, so my question is > whether this is caused by timeresolution problems within either ping or > ppp; or I'm just plain lucky to hit n*10 every time? :) Sounds like it could be the other end. What's there? I seem to remember that System V STREAMS can sometimes do things like this. BTW, for normal ping packets and 33.6 or 56 kb/s, these are *very* slow times. Greg -- Finger grog@lemis.com for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19991125173107.16398>