[186866] in North American Network Operators' Group
Re: Smokeping targets
daemon@ATHENA.MIT.EDU (Keith Stokes)
Thu Jan 7 11:46:39 2016
X-Original-To: nanog@nanog.org
From: Keith Stokes <keiths@neilltech.com>
To: Jon Lewis <jlewis@lewis.org>
Date: Thu, 7 Jan 2016 16:45:00 +0000
In-Reply-To: <Pine.LNX.4.61.1601071045450.10544@soloth.lewis.org>
Cc: "nanog@nanog.org" <nanog@nanog.org>
Errors-To: nanog-bounces@nanog.org
I have a couple of different SmokePing implementations related to our SaaS =
platform.
I have monitors inside our network looking at several of our largest custom=
ers.
I have monitors in some IaaS providers looking back at us.
I do include a couple of common addresses previously mentioned since I need=
some sort of confirmation to show the sites can actually get out.
On Jan 7, 2016, at 10:24 AM, Jon Lewis <jlewis@lewis.org<mailto:jlewis@lewi=
s.org>> wrote:
On Thu, 7 Jan 2016, Brian R. Swan wrote:
Hi all,
I=FF=FFm setting up smokeping to try and gather some latency statistics on =
my ISP to different parts of the world. Does there exist a list or any gen=
eric recommendations of different targets to config within smokeping? Googl=
e and searching the NANOG mailing list have failed me, and I don=FF=FFt wan=
t to just spam random IP addresses with ICMP requests if there=FF=FFs a mor=
e official/accepted method for doing this.
8.8.8.8 is pretty popular. There's lots of them. (Anycast)
But, it's not nice to send remote networks unwanted traffic (it's a DNS ser=
ver, not a light house), and I know GOOG receives enough ICMP at some of th=
ose anycast nodes to be "problematic".
I'd say keep your smokeping targets to devices you or your connectivity pro=
vider(s) own/are paying for rather than abusing random 3rd parties just to =
satisfy your curiosity.
----------------------------------------------------------------------
Jon Lewis, MCP :) | I route
| therefore you are
_________ http://www.lewis.org/~jlewis/pgp for PGP public key_________
---
Keith Stokes
