- ripe-atlas - mailman.ripe.net

Anchors and NTP back to the future
by Stephane Bortzmeyer 23 Oct '15

23 Oct '15

Some anchors appear to be reachable with NTP but most of them are not. I guess it means the anchor always has a NTP server (and I assume it is on purpose) but many networks filter it. What is the good recommanded practice? Specially in the light of the Back to the Future attack <http://www.cs.bu.edu/~goldbe/NTPattack.html>

1 0

Public vs. Non-Public Probes
by Vesna Manojlovic 22 Oct '15

22 Oct '15

Hi Jonathan and others, Thanks for bringing this point up again. I hope others will feel free to join in the discussion. As Wilfried mentioned, we did have a discussion about public and non-public probes some time ago. Here are the relevant posts: RIPE Labs article proposing making RIPE Atlas probes and measurements more public: https://labs.ripe.net/Members/becha/proposing-making-ripe-atlas-data-more-p… Discussion on the ripe-atlas list: https://www.ripe.net/ripe/mail/archives/mat-wg/2013-December/000399.html Conclusion: https://www.ripe.net/ripe/mail/archives/mat-wg/2014-March/000436.html Consequences: new terms & conditions, with more clarification on this topic: https://labs.ripe.net/Members/becha/ripe-atlas-moving-to-production-service & https://atlas.ripe.net/legal/terms-conditions/ As you can see from the discussions above, some RIPE Atlas users felt it was important to retain the choice of marking their probes “non-public”. We do encourage all RIPE Atlas users to mark their probes “public” for the greatest benefit to the community, and the majority of probes are public. However, non-public probes are still used both for built-in measurements and user-defined measurements; they are just not listed on the web or API. Once a user decides to plug a probe into their network, IP address information can no longer remain "private". This is why we prefer to refer to them as “non-public” probes rather than truly “private” probes. Of course, we care very much about protecting probe hosts’ privacy and we never make personal information like email addresses or MAC addresses public. There is some more information about this in the FAQs on the RIPE Atlas website under the answers to "Will my IP address show up in measurements done by my probe?” and "Is the measurement data made public?”, but the RIPE Labs article referenced above contains the most detailed information on the topic. Thanks again for your thoughts on this, and please let us know if you have any other questions or comments. Regards, Vesna

2 1

Prove v3 not connecting after powercyle
by Jeroen Bogers 20 Oct '15

20 Oct '15

Hi all, Two days ago I had to powercycle some of my network equipment, including my Atlas V3 probe. After the powercycle, the probe did not come back online. After booting, the first and second light (power and the one next to it) remain lit (not blinking). This is not a state that is listed in the FAQ: https://atlas.ripe.net/about/faq/#what-do-the-lights-on-the-side-of-the-pro… The only status that comes close is the 'Running from built-in flash' state, but led 2 should be blinking then? Does someone here have an idea what is wrong with my probe (and how to fix it)? I already tried connecting it to a different network port and power source, but this did not make any difference. The switch port the probe is connected to does light up, so the Ethernet port seems to be functioning. With kind regards, Jeroen Bogers

1 0

[Feature Request] Show probe address on failure notifications
by Brian Rak 16 Oct '15

16 Oct '15

I recently received one an email indicating one of my probes is offline: This is the second reminder that your probe (#20689 ) is not connected to our infrastructure and has been disconnected since 2015-09-14 09:37 UTC. Could you please check whether everything is set up correctly on your side? If it is, and your probe is still reported as disconnected when you log in at https://atlas.ripe.net, please reply to this email so that we can follow up. Is there any way these can be modified to include further information (like the probe's address, or basically anything about it)? Probe 20689 means nothing to me, so I have to log in to take a look at exactly what it is, and where I need to go to fix it.

2 2

New on RIPE Labs: Researching F-root Anycast Placement Using RIPE Atlas
by Michela Galante 14 Oct '15

14 Oct '15

Dear colleagues, Please find a new article on RIPE Labs: https://labs.ripe.net/Members/ray_bellis/researching-f-root-anycast-placeme… In order to expand the reach of F-root, Ray Bellis looked at where queries to F-root are coming from and where it would make most sense to place new nodes. As a first step, Ray looked at the existing nodes to see how they behave and if there is anything that can be improved. He used RIPE Atlas to do this. Kind regards, Michela Galante RIPE NCC

1 0

More built in IPv6 tests
by Brzozowski, John 12 Oct '15

12 Oct '15

Would it be possible to include some new built in measurements for the following: * IPv6 only capable * IPv6 preferred (and perhaps IPv6 capable, this is different than IPv6 only capable above) * Compare IPv4 and IPv6 performance over HTTP John +1-484-962-0060 -----Original Message----- From: ripe-atlas <ripe-atlas-bounces(a)ripe.net> on behalf of Robert Kisteleki <robert(a)ripe.net> Organization: RIPE NCC Date: Sunday, October 11, 2015 at 05:04 To: Alarig Le Lay <alarig(a)grifon.fr>, "ripe-atlas(a)ripe.net" <ripe-atlas(a)ripe.net> Subject: Re: [atlas] IPv6 only >On 2015-10-10 20:15, Alarig Le Lay wrote: >> Hi, >> >> Are the probes able to run on an IPv6 only network? I’ve configured one >> and left the default IPv4 configuration (i.e. DHCP) but the probe is not >> marked as running in the web interface. >> >> Regards, > >Hi, > >The short answer is yes, the longer one is in the FAQ: >https://atlas.ripe.net/about/faq/#i-have-an-ipv6-only-network-will-the-pro >be-work-on-it > >Regards, >Robert > >

1 0

IPv6 only
by Alarig Le Lay 11 Oct '15

11 Oct '15

Hi, Are the probes able to run on an IPv6 only network? I’ve configured one and left the default IPv4 configuration (i.e. DHCP) but the probe is not marked as running in the web interface. Regards, -- Alarig Le Lay

2 1

3rd generation probe doesn't appear as online
by Thiago Ayub 08 Oct '15

08 Oct '15

Hi, I receive a week ago our first probe but I'm unable to make it appear as online at the website. I can see it requests DHCP, it gets an IP address (NATed), it does some measurements (like HTTP and NTP) successufly but at atlas.ripe.net it is listed as 'Never online'. It rebooted around 3 times in the last week and each time was kept as least 24h in a row with no power down or cable disconnect. The MAC ADDRESS at the website matches with the MAC ADDRESS labeled in the probe. How should I proceed to get this fixed? Best regards, Thiago Ayub

7 9

Permanent private measurement
by Lorenzo Colitti 08 Oct '15

08 Oct '15

Hi Atlas folks, I'd like to use my probe to monitor the status of my home Internet connection by continuously pinging my ISP's network (which is not the first or second hop in traceroute, but something like the sixth) and perhaps www.google.com. Is there a way to do this easily using the existing UI and tools? I couldn't find any existing measurements for this. I can look at the built-in v4 and v6 measurements for K-root, which is normally very close to me, but that's not 100% representative of the status of my Internet connection because it also measures the peering exchange link between my ISP and K-root. Cheers, Lorenzo

4 6

Join RIPE Atlas Hackathon - 14-15 November - Bucharest
by Vesna Manojlovic 05 Oct '15

05 Oct '15

Calling all software developers, designers and network operators! The next RIPE Atlas hackathon takes place 14-15 November in Bucharest, right before RIPE 71. We're looking for creative thinkers to help us find new ways to use RIPE Atlas data to monitor networks and troubleshoot issues as well as ways to improve the existing toolset. Is this you? Then we want to hear from you! ----------------------- How to Apply ----------------------- The application form is online at: https://atlas.ripe.net/hackathon/tools-2015/#!application-form *The deadline to apply is Tuesday, 6 October* Successful applicants will: - Work alongside RIPE Atlas engineers - Get to know others in your field - Contribute to the shared code - Exchange knowledge and experience All source code developed during the hackathon will be publicly licensed and available on GitHub, and will be free for the entire community to use. ---------------------- Hackathon details --------------------- Date: 14-15 November 2015 Time: Saturday 09:00-19:00, Sunday 09:00-21:00 (including party) Location: JW Marriott Bucharest Grand Hotel, Bucharest, Romania Applicants will hear back from the jury on 12 October so that travel arrangements can be made on time. Find out more on RIPE Labs: https://labs.ripe.net/Members/becha/join-the-ripe-atlas-tools-hackathon -------------------- Call for Sponsors ------------------- We are still looking for sponsors! Is your organisation interested in supporting our efforts? Please email me promptly and directly – thank you! I look forward to seeing you there! Regards, Vesna

1 2