June 2013 - ripe-atlas - mailman.ripe.net

troubleshooting a new probe configuration
by Allison, Jared M 18 Jun '13

18 Jun '13

Hello, I just got a new RIPE Atlas probe at NANOG in New Orleans, US and am trying to get it up and running. I configured a port for it on my firewall with IPv4 DHCP service and DNS. The firewall rules should permit just about all traffic. I confirmed that the port was operational by connecting a computer to it and could browse to external websites, etc. When I connect the probe to this port, I can see in the logs that it gets an IPv4 DHCP address, but doesn't seem to do anything else. The power light on the probe is solid, the second light appears to be off, and the third and fourth lights are blinking. It's been this way through several power-cycles and several days. Any idea what error condition this indicates? Thanks, -jared --- Jared Allison jared.allison(a)verizon.com

1 0

BOOTP/DHCP on a probe with static network configuration
by Jay Borkenhagen 18 Jun '13

18 Jun '13

Hi, I have two brand new RIPE Atlas probes. Both are reported as 'connected' on my My Atlas page, both run the 4520 firmware, and both correctly report and use the static network configurations I gave them per the instructions at https://atlas.ripe.net/doc/static-config However, both probes still send BOOTP/DHCP requests every 3 seconds. Are others seeing this behavior with their probes that have static network configurations? Can this behavior be changed? Thanks! Jay B.

1 1

A New look, a tailor made hospitality - Welcom and Welcome back
by Hotel Pioppeto saronno 16 Jun '13

16 Jun '13

+39.0296248164 pioppeto(a)hotelpioppeto.it WWW.HOTELPIOPPETOSARONNO.IT Via Strà Madonna, 15 - 21047 Saronno (VA) - A9 Milano-Como-Chiasso motorway, Saronno exit

1 0

A New look, a tailor made hospitality - Welcom and Welcome back
by Hotel Pioppeto saronno 12 Jun '13

12 Jun '13

+39.0296248164 pioppeto(a)hotelpioppeto.it WWW.HOTELPIOPPETOSARONNO.IT Via Strà Madonna, 15 - 21047 Saronno (VA) - A9 Milano-Como-Chiasso motorway, Saronno exit

1 0

New Atlas Probe
by Lee Hetherington 10 Jun '13

10 Jun '13

Hi, I obtained an Atlas probe at NANOG last week... I've got it connected (natted) and registered, but it's not showing up under my probes as yet. How long does it usually take? I can see traffic on the port that i've connected the atlas probe too, so assume its able to get out. Cheers, Lee

5 4

Newly-defined traceroute measurement failing with "name resolution failed: non-recoverable failure in name resolution"
by Bill Fenner 04 Jun '13

04 Jun '13

Hi, I have two probes that seem to work just fine; their built-in measurements work, I can see their results from my "My Atlas" page, etc. I happened to notice something weird about the ping times to c.root-servers.net, so wanted to define a traceroute measurement to see if there were route changes that could explain what I saw. However, the only result that I'm getting is "error": "name resolution failed: non-recoverable failure in name resolution". I picked "Resolve on probe", and used "c.root-servers.net" as the destination. I'm pretty sure I didn't make a typo, because I've copy-n-pasted from the dst_name of the result JSON. For reference, the UDM ID is 1010361 and the probes are 4936 and 4938. Each probe has a working DNS server configured, according to the "My Probes" view. Thanks for any help, Bill (P.S. I created a new UDM using the IP address, to work around the DNS problem, but it'd still be nice to understand what I did wrong with the other one.)

2 1