Date: Sat, 16 Aug 2003 03:30:45 -0400 From: "Eric W. Bates" <ericx@vineyard.net> To: "Tom ONeil" <tom.oneil@tacni.com> Cc: "freebsd-isp@freebsd.org" <freebsd-isp@FreeBSD.ORG> Subject: Re: Website response time problem Message-ID: <006f01c363c8$4e5024b0$3ee380cc@alice> References: <3F3C400B.9020300@tacni.com>
next in thread | previous in thread | raw e-mail | index | archive | help
It can take a bit of doing; but smokeping gives a picture that customers generally can understand. In the case of this cable customer you might even be able to display his personal latency (if his IP stays stable for a week or so). ----- Original Message ----- From: "Tom ONeil" <tom.oneil@tacni.com> To: "freebsd-isp@freebsd.org" <freebsd-isp@FreeBSD.ORG> Sent: Thursday, August 14, 2003 10:06 PM Subject: Website response time problem > Is there something quick & dirty in ports I can use to prove to a client > it's his cable modem and not the backbone ? > Looking for something along the lines of a timed http get. > > ntop didn't convince him - too complex. sntop is just ping. > I have access to other backbones & carriers to run it from, just > wondering what there is. > > Best Regards, > > Tom > -- > Thomas J. ONeil tom.oneil@tacni.com > http://www.tacni.net > "National Power, Local Presence" > > _______________________________________________ > freebsd-isp@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-isp > To unsubscribe, send any mail to "freebsd-isp-unsubscribe@freebsd.org" >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?006f01c363c8$4e5024b0$3ee380cc>