Smokeping targets

Fri Jan 8 18:23:08 UTC 2016

Most of these "OMG, think of the target!!!!!111" posts are unwarranted. The OP asked for lists of IPs that the community agrees can be safely monitored. If it can be safely monitored , obviously the host is aware and agrees to it. 

Yes, if a particular hop along the way has a higher latency than ones behind it, it's just an overloaded control plane.... but that network should be looking to upgrade that router anyway. (Cue the OMG, it's forwarding just fine e-mails... don't.) 

----- 
Mike Hammett 
Intelligent Computing Solutions 
http://www.ics-il.com 

Midwest Internet Exchange 
http://www.midwest-ix.com 

----- Original Message -----

From: "Marco d'Itri" <md+nanog at Linux.IT> 
To: nanog at nanog.org 
Sent: Thursday, January 7, 2016 10:13:58 AM 
Subject: Re: Smokeping targets 

On Jan 07, Andrew Dampf <adampf at gmail.com> wrote: 

> Something I found that is helpful once you've gathered a list of targets is 
> the following command for generating config to paste: 
> 
> traceroute -w 3 [IPaddress] | grep -v "*" | grep -v "traceroute" | sed -e 
> 's/(//g' -e 's/)//g' | awk '{ gsub(/\./,"_",$2); print "++++ "$2"\nmenu = 
> "$3"\ntitle = "$2" - "$3"\nhost = "$3"\n"}' 
> 
> That generates a valid output for configs to ping each hop along the way to 
> your destination, which can be super useful. Not all of them allow ICMP but 
> a decent amount do. 
It is also super stupid, because routers reply to ICMP echo requests 
with a very low priority: this introduces jitter which makes these 
measurements unreliable. 
If you are not monitoring a server then you are wasting your time. 

(Also, it would be nice to have the owner permission before deciding to 
permanently send a lot of ICMPs to a device.) 

-- 
ciao, 
Marco 