- ripe-atlas - mailman.ripe.net

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

19 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

Atlas probe - virtual appliance?
by Daniel Suchy 19 Jun '13

19 Jun '13

Hello, maybe should be interesting providing RIPE Atlas probe as an virtual appliance (VMWare, XEN, VirtualBox etc). Handling will be much easier and deployment cheaper (as no extra hardware will be required to run new probe). Virtual apliance should be still managed by RIPE NCC (like current hardware probes) in terms of upgrades and so on. I think this may be interesting to consider. With regards, Daniel

7 7

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

Troubles with registering the probe if assigned by Ambassador
by Alex Saroyan 29 May '13

29 May '13

Hi, I'm not sure, but seems that if the probe was initially assigned to ambassador then ambassador assigned to the host the probe in not appearing in host's account. Example 1 Probe F81A674D7482 was assigned to levon.avagyan(a)gmail.com by me ambassador alex.saroyan(a)gmail.com. In Ambassador page I see this probe as "Online, not hosted", and host does not see the probe on his account at all. Example 2 Probe A0F3C1C44063 was assigned to surenispiryan(a)gmail.com again by me ambassador alex.saroyan(a)gmail.com. He didn't connect the probe yet to network. In Ambassador page I see the probe status "Applied" and host does not see the probe in his account under "my probes" at all. Regards. /Alex

6 15

[ripe.net #1087678] problem with connection to network
by Alastair Strachan 28 May '13

28 May '13

Hello, Thanks for your email and update. I can confirm the probe is back online and reporting without issue. If you do have any further questions, please do not hesitate to contact us. Thank you for taking the time to host an Atlas probe. Kind Regards, Alastair Strachan RIPE Atlas Team ============================================================ Take the RIPE NCC Survey 2013 and tell the RIPE NCC what you think! Participants will be entered into prize draws to win an iPad. https://www.ripe.net/survey2013 ============================================================= On Mon May 27 18:33:28 2013, sdimonius(a)gmail.com wrote: > Hello and thanks for reply! > > Now probe is work. I was read all FaQ, but nothing help. > > The network is efficient for 100%. > > Experiments help me. First i remove external memory, boot from built > in, > and then attach usb flash, after 10 mins probe connect to network. > > 27.05.2013 16:23, Alastair Strachan пишет: > > Hello, > > > > Thanks for your email and update. > > > > It would appear there is something on the network that is blocking > the probe from connecting outside the network. > > > > If a probe has been assigned a Static IP and for some reason that is > not reachable, the probe will automatically fall back to DHCP. As this > is not happening, there must be something blocking it. > > > > The probe is currently configured via DHCP, again, this is not > allowing the probe to connect outside your network. > > > > Please ensure port 443 is fully open and all firewall/security rules > have been adjusted accordingly. Please take a look at our FAQ for more > troubleshooting steps: https://atlas.ripe.net/about/faq/ > > > > If you do have any further questions, please do not hesitate to > contact us. > > > > Thank you for taking the time to host an Atlas probe. > > > > Kind Regards, > > > > Alastair Strachan > > > > RIPE Atlas Team > > > > ============================================================ Take > the RIPE NCC Survey 2013 and tell the RIPE NCC what you think! > > Participants will be entered into prize draws to win an iPad. > > https://www.ripe.net/survey2013 > ============================================================= > > > > > > > > > > > > On Sun May 26 16:01:00 2013, sdimonius(a)gmail.com wrote: > >> Hello! > >> > >> I have problem with my probe v3 (ID 11003, FW 4520). > >> > >> First i used DHCP (at Home, for tests), all was worked fine. > >> > >> Then i reconfigure my probe to Static IP (by manual). Static IP > >> necessary to install my probe 24/7/365 in server room. We don't use > DHCP. > >> > >> But probe can't connect to network... > >> > >> I brought probe to home, connect to DHCP network. Router give IP to > >> probe. But probe still disconnected on atlas.ripe.net at least 3 > hours... > >> > >> LEDs: > >> 1 - ON > >> 2 - OFF > >> 3 - Slow blink > >> 4 - ON > >> 5 - ON > >> > >> Power reset - no result. Try to change Router cfg (ip, dns, mask) - > no > >> result. Probe still disconnected. > >> > >> I read, that if set static IP - probe try to test setting. > >> > >> By LEDs - "Network test"? But 3+ hours "Network test"? > >> > >> DHCP work correctly (Router - Zyxell Keenetic, last firmware), PC > work > >> without problems on full autoconfiguration (IP, mask, gateway, DNS) > >> > >> Can you help me? > >> > >> P.S. Sorry for my english, i'm from Ukraine > >> > >> > >> > > > > > >

5 4