Re: Smokeping targets

[Mike Hammett]

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"  
To: nanog@nanog.org 
Sent: Thursday, January 7, 2016 10:13:58 AM 
Subject: Re: Smokeping targets 

On Jan 07, Andrew Dampf  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 

Re: Smokeping targets

[Marco d'Itri]

On Jan 07, Andrew Dampf  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


signature.asc
Description: PGP signature

Re: Smokeping targets

[Brian R. Swan]

Doh!  Not sure why I didn’t think about Atlas prior to posting my question - 
that’s perfect.  

I have an Atlas node on my network too.  After I put it in and played with it 
for a week I started a big project at work and put it on the “to play with 
later” list and never got back to it. :)

Thanks!
Brian

> On Jan 7, 2016, at 10:26 AM, Frederik Kriewitz  wrote:
> 
> Hello Brian,
> 
> you might want to consider joining the nlnog ring (https://ring.nlnog.net/ 
> ).
> You can request access to a full mesh smokeping for all hosts too.
> 
> Besides the ring host RIPE Atlas anchors 
> (https://atlas.ripe.net/anchors/list/ ) 
> might be another option for hosts to add to your list.
> 

Re: Smokeping targets

[Clinton Work]

The NLNOG RING servers would be good targets and they expected to get
pinged.   
https://ring.nlnog.net/participants/

On Thu, Jan 7, 2016, at 08:34 AM, Brian R. Swan wrote:
> I’m 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
> generic recommendations of different targets to config within smokeping? 

Re: Smokeping targets

[Frederik Kriewitz]

Hello Brian,

you might want to consider joining the nlnog ring (https://ring.nlnog.net/).
You can request access to a full mesh smokeping for all hosts too.

Besides the ring host RIPE Atlas anchors (
https://atlas.ripe.net/anchors/list/) might be another option for hosts to
add to your list.
Am 07.01.2016 16:36 schrieb "Brian R. Swan" :

> Hi all,
>
> I’m 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
> generic recommendations of different targets to config within smokeping?
> Google and searching the NANOG mailing list have failed me, and I don’t
> want to just spam random IP addresses with ICMP requests if there’s a more
> official/accepted method for doing this.
>
> Thanks!
> Brian

Re: Smokeping targets

[Brian R. Swan]

Very cool - thanks for sharing that.

> On Jan 7, 2016, at 9:59 AM, Andrew Dampf  wrote:
> 
> Something I found that is helpful once you've gathered a list of targets is 
> the following command for generating config to paste:

Re: Smokeping targets

[Andrew Dampf]

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.

On Thu, Jan 7, 2016 at 10:34 AM, Brian R. Swan  wrote:

> Hi all,
>
> I’m 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
> generic recommendations of different targets to config within smokeping?
> Google and searching the NANOG mailing list have failed me, and I don’t
> want to just spam random IP addresses with ICMP requests if there’s a more
> official/accepted method for doing this.
>
> Thanks!
> Brian