- ripe-atlas - mailman.ripe.net

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

probe probed
by Gary Gapinski 02 Oct '15

02 Oct '15

Saw my first IPv6 port scan recently, targeting my domestic Atlas probe. Originated from Shodan, first seen 2015-09-30T2017Z, and again ~24 hours later. At the moment, the probe is behind a stateful firewall (which dropped the traffic). Does it make any difference if it were moved to be completely exposed? (I've often wondered whether this should be the case to ensure proper function.) It is behind (filtered) NAT on the IPv4 side. Regards, Gary

2 1

RIPE Atlas probe archive not currently working
by Chris Amin 02 Oct '15

02 Oct '15

Dear RIPE Atlas users, We are aware that the archive of RIPE Atlas probe metadata has not been available since code changes on Wednesday afternoon. This affects both the archive API at /api/v1/probe-archive/ and recent days in the FTP archive at http://ftp.ripe.net/ripe/atlas/probes/. If you only require old archives (Tuesday 29th September and older), you can fetch them from the FTP site as usual. We are working on restoring this functionality as quickly as possible. Please accept our apologies for any inconvenience that this may have caused. Kind regards, Chris Amin RIPE NCC

1 1

Iran and K-root - The Rest of the Story
by Vesna Manojlovic 01 Oct '15

01 Oct '15

Dear colleagues, Dyn Research published an article on K-root recently. Here we would like to augment the picture with data from RIPE Atlas in order to provide a more complete picture of the effect of the K-root node in Iran. Please find the results on RIPE Labs: https://labs.ripe.net/Members/emileaben/iran-and-k-root-the-rest-of-the-sto… Kind regards, Vesna

1 0

Leaseweb Network B.V. (Frankfurt, Germany) has joined RIPE Atlas Anchors
by Michela Galante 29 Sep '15

29 Sep '15

Dear RIPE Atlas users, We're happy to announce that another RIPE Atlas anchor has joined the network and is now available as a target for probe hosts conducting their own user-defined measurements. The new anchor is called de-fra-as28753 and it is hosted by Leaseweb Network B.V. in Frankfurt, Germany. Congratulations to Leaseweb Network for their second anchor online! Anchoring measurements (ping, ping6, traceroute and traceroute6) are scheduled towards this anchor from all the other anchors as well as several hundred probes, providing a continual overview of regional reachability. Results of these measurements are available as raw data in JSON format, and visualised on the map and "seismograph" with many configurable features. You can access the anchoring measurements for all anchors at: https://atlas.ripe.net/anchors/list/ Learn more about RIPE Atlas anchors at: https://atlas.ripe.net/about/anchors/ Thank you for participating in RIPE Atlas! Kind Regards, RIPE Atlas Team atlas(a)ripe.net

1 0

Liquid Web (Haarlem, Netherlands) has joined RIPE Atlas Anchors
by Michela Galante 28 Sep '15

28 Sep '15

Dear RIPE Atlas users, We're happy to announce that another RIPE Atlas anchor has joined the network and is now available as a target for probe hosts conducting their own user-defined measurements. The new anchor is called nl-haa-as201682 and it is hosted by Liquid Web in Haarlem, Netherlands. Congratulations to Liquid Web for their third anchor online! Anchoring measurements (ping, ping6, traceroute and traceroute6) are scheduled towards this anchor from all the other anchors as well as several hundred probes, providing a continual overview of regional reachability. Results of these measurements are available as raw data in JSON format, and visualised on the map and "seismograph" with many configurable features. You can access the anchoring measurements for all anchors at: https://atlas.ripe.net/anchors/list/ Learn more about RIPE Atlas anchors at: https://atlas.ripe.net/about/anchors/ Thank you for participating in RIPE Atlas! Kind Regards, RIPE Atlas Team atlas(a)ripe.net

1 0

Possible reasons behind a failed measurement
by Wenqin SHAO 28 Sep '15

28 Sep '15

Dear list, I recently launched a ping measurement that selects 50 anchors worldwide for a period of 24 hours, id 2439518. The measurement failed with no probe allocated to it. Do you have any clue on the possible reasons for that? One of my guesses is that anchors are highly demanded and non of them were available during the measurement window. I’d love to hear you thinkings on this matter. Many thanks for your attention. Best regards, Wenqin Shao ---- Ph.D candidate Telecom ParisTech

3 3

Fwd: Byte Night Manchester - Action for Children - donation help needed please :)
by Colin Johnston 28 Sep '15

28 Sep '15

Hopefully IT folks will donate to this great cause, hopefully folks will allow this posting :) > Begin forwarded message: > > From: <colin.johnstone(a)bt.com> > Date: 28 September 2015 at 08:12:03 BST > To: <colinj(a)gt86car.org.uk> > Subject: FW: Byte Night Manchester - Action for Children - donation help needed please :) > > > > > > Dear all, > As my regular yearly charity participation event please support below > Byte Night Manchester - BT Manchester folks – Colin team of one. > > On Friday night next, 2nd Oct 2015 from 7pm to 6am next morning, I (Colin Johnston) am participating in > Action for Children Byte Night Manchester. > As we have been asked to dress up for nice social media pictures I decided that being dressed as a Sylvester Cat > would be good fun. > I have managed to get http://celebrationpartyshoponline.co.uk/stores <http://celebrationpartyshoponline.co.uk/stores> to give me a discount on the costume hire as well. > The Byte Night for Manchester is being held at Granada Studios in Manchester on the street of Coronation Street. > > We(Byte Night participants) are sleeping on the street in sleeping bags and foil survival bag. > > Please donate to this great cause, either by donation bucket in BT Bolton AMTE (Sylvester will be in Bolton on Thursday/Friday) or > BT Dial House Manchester (Sylvester will make a visit on Friday), > or via internet https://www.justgiving.com/bt-bt-manchester-folks/4w350m3/donate#MessageAnd… <https://www.justgiving.com/bt-bt-manchester-folks/4w350m3/donate#MessageAnd…> > > Please email me colin.johnstone(a)bt.com <mailto:colin.johnstone@bt.com> if donation made so I can keep track of donators list. > I want to transfer the total raised to Action for Children by middle of Oct so please give money via above either this week coming or next. > I will email folks with acknowledgement of final donation amount once received, would be great to get 500 pounds ++.. > > Pictures will be sent after the event for BT Today and all on this email to listJ > > Please give generously if you can afford it, pay day on Wednesday J > > Please distribute widely if you think others not mentioned would be willing to donate JJ > > Yours > > Colin Johnston

1 0

Question about unstable power and probe
by Anurag Bhatia 27 Sep '15

27 Sep '15

Hello everyone! I have recently deployed a probe in a place where there's unstable power. Probe is rebooting like 4-5 times a day and unlikely power would be fixed in near future. I was wondering if it's safe for probe at all. Does anyone has experience with 4-5 reboots a day with probe? Will probe sustain it or better I just disconnect it and rather wait for power to become stable? Curious to hear your experiences. Thanks. -- Anurag Bhatia anuragbhatia.com PGP Key Fingerprint: 3115 677D 2E94 B696 651B 870C C06D D524 245E 58E2

3 2

Save the date: RIPE Atlas Hackathon - 14-15 November - Bucharest
by Vesna Manojlovic 25 Sep '15

25 Sep '15

Dear all, It’s official: we will hold a new RIPE Atlas hackathon on the weekend before RIPE 71 in Bucharest. Join us, along with network operators and software developers from the Internet community, to work on RIPE Atlas tools. You'll have the chance to work alongside RIPE Atlas developers, meet others in your field, and 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. 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 We are looking for sponsors! Is your organisation interested in supporting our efforts? Please email me promptly and directly – thank you! Finally, stay tuned - this is a pre-announcement. We will publish more details, along with the application form, early next week. I look forward to seeing you there! Regards, Vesna

1 0

New on RIPE Labs: Time Travel with RIPE Atlas
by Vesna Manojlovic 25 Sep '15

25 Sep '15

Dear colleagues, Please find another new RIPE Atlas related article on RIPE Labs: RIPE Atlas users can now use a new feature on the maps to travel back in time: https://labs.ripe.net/Members/suzanne_taylor_muzzin/ripe-atlas-time-travel-… Kind regards, Vesna

1 0

Latest three RIPE Labs articles about RIPE Atlas
by Vesna Manojlovic 24 Sep '15

24 Sep '15

Dear colleagues, there have been many new articles published on RIPE Labs: about RIPE Atlas features, using RIPE Atlas data for analysis, etc. Please find the info about the latest three in this email, and many more here: https://labs.ripe.net/atlas Regards, Vesna Looking at France-IX with RIPE Atlas and RIS, by Emile Aben Sep 24, 2015 10:09 AM This article describes our recent collaborations with France-IX on collecting data plane and control plane Internet data with RIPE Atlas and the RIPE NCC's Routing Information Service (RIS): https://labs.ripe.net/Members/emileaben/looking-at-france-ix-with-ripe-atla… New RIPE Atlas Tool: LatencyMON, by Massimo Candela Sep 23, 2015 10:10 AM LatencyMON is a new RIPE Atlas web application that you can use to easily visualise and compare multiple latency trends collected by groups of RIPE Atlas probes. https://labs.ripe.net/Members/massimo_candela/new-ripe-atlas-tool-latencymon Checking your Internet Connectivity with RIPE Atlas Anchors, by Stéphane Bortzmeyer Sep 14, 2015 05:05 PM If you monitor your external Internet connectivity, you may wonder which machine is the best to ping. Hesitate no more - you can use RIPE Atlas anchors as landmarks. https://labs.ripe.net/Members/stephane_bortzmeyer/checking-your-internet-co…

1 0

NIX.CZ (Czech Republic) has joined RIPE Atlas anchors
by Michela Galante 24 Sep '15

24 Sep '15

Dear RIPE Atlas users, We're happy to announce that another RIPE Atlas anchor has joined the network and is now available as a target for probe hosts conducting their own user-defined measurements. The new anchor is called cz-prg-as6881 and it is hosted by NIX.CZ in Prague, Czech Republic. Anchoring measurements (ping, ping6, traceroute and traceroute6) are scheduled towards this anchor from all the other anchors as well as several hundred probes, providing a continual overview of regional reachability. Results of these measurements are available as raw data in JSON format, and visualised on the map and "seismograph" with many configurable features. You can access the anchoring measurements for all anchors at: https://atlas.ripe.net/anchors/list/ Learn more about RIPE Atlas anchors at: https://atlas.ripe.net/about/anchors/ Thank you for participating in RIPE Atlas! Kind Regards, RIPE Atlas Team atlas(a)ripe.net

1 0

Downloading ad-hoc Atlas measurements as JSON
by Jonathan Brewer 24 Sep '15

24 Sep '15

Hi All, One of my current frustrations is that when downloading ad-hoc Atlas measurements, the file name is always the same: "RIPE-Atlas-measurement.json". This is unfortunate. It would be great if the web server would by default call this measurement by its ID. Anyone else experiencing this problem? Regards, Jon

5 6

Maintenance works today
by Robert Kisteleki 24 Sep '15

24 Sep '15

Dear All, We'll carry out maintenance work on the core RIPE Atlas infrastructure today, approximately between 10-11h Amsterdam time (8-9 UTC). This will also affect the API/UI, most likely resulting in failed API calls or web page loads. Excuses for the inconvenience. Regards, Robert Kisteleki

1 0

RIPE Atlas Tools and Python versions
by Daniel Quinn 24 Sep '15

24 Sep '15

As some of you may already know, we’ve been working on a new command-line toolkit that will let you do nifty things like: * List measurement and probe metadata * Generate reports from measurement results * Stream measurement results It’s coming along quite nicely, but I’m running into just too many cases where support for Python 2.6 is (a) making my job harder, and (b) making my code uglier. Given that (a) means I spend more time fixing compatibility rather than adding features and (b) just makes me sad, I wanted to ask the community how important Python 2.6 is to you. So here’s the question: Of those of you who would find such a tool interesting/useful, how many of you *only* have access to a computer running Python 2.6? Such systems include CentOS distributions earlier than 7, and corresponding RedHat Enterprise systems. If you’re using Debian, or Ubuntu, you should already have 2.7 by default, and if you’re on Gentoo or Arch, you probably have both 2.7 and 3.5 already. I understand that Apple’s OSX is running 2.7 these days as well. If I don’t get a wave of messages about how very important 2.6 is to your collective health and wellbeing, I’m going to consider this a non-issue and drop support for 2.6. Thanks for your input everyone :-)

5 5

Friday's events on RIPE Atlas
by Romeo Zwart 23 Sep '15

23 Sep '15

Dear all, Here is a description of the events that took place last Friday and some 'lessons learned' that we took away from it. The high level summary of events is that an Atlas user was authorised to create an extreme number of measurements involving a large number of probes. This effectively overloaded the back-end machinery in various different ways. Even though this event could only happen because of the exception in resource use limits, we have implemented workarounds and countermeasures to avoid a repetition in future, and we will be investigating some of the more fundamental issues in the coming period. More information is available below for those interested. Observations: - Problems started shortly before 11am when one of the Atlas users created a large number of new measurements each involving all available probes. The user had been given an exceptional amount of credits as part of a special experiment. Therefore the normal limitations on the impact any individual user can have on the system were not active when the measurements were created and activated. - The results of the newly created measurements put a lot of strain on the measurement scheduler, which triggered our interest. After some investigation the cause of the overload was identified and the related measurements were ended. - However, by this time the majority of results, up to that moment, had already reached our queuing servers and the consumers were already ingesting the results into our Hadoop storage platform. - At this phase we discovered a capacity problem with the process that consumes the Atlas results, so we doubled the capacity of that component on the fly. - This exposed the next bottleneck in our platform in the form of an accumulation of the created results on a very small number of processing nodes. Normally the incoming measurement results are distributed over several storage nodes, so this strongly reduced the consumption rate of new data. - A third factor that contributed was the fact that, in attempt to curb growth of the Atlas data, we have migrated the Atlas data sets to a more efficient compression algorithm earlier in the year. This saved us some 40-50% of storage space for the Atlas data, at the expense of some compute power. Under normal circumstances, even at high loads, this compute power is abundantly available on the storage cluster. Under the specific circumstances of last Friday's events, it turned out that the change of the compression algorithm had increased processing time for some Hadoop system tasks by up to a factor of 8, which had a direct impact on the data consumption speed. Immediate actions taken: - Removed special privileges of the end-user in question - Added capacity to the Atlas consumer processes - Returned (temporarily) to less efficient compression on the Atlas data sets. Lessons learned and further planned action: - Granting special privileges for some of the Atlas users needs (even) more attention than it already receives. - We need to better communicate "best practices" to these power users so they can use their extra allowances responsibly. - Improved compression of Atlas data has decreased our storage demands but also decreased our processing capacity. This needs further investigation to find the optimum configuration. - Investigate possibilities to better spread incoming results over more worker nodes (reduce hotspots). - Investigate and quantify reasonable boundaries of scalability of the whole system, to guide the limits for granting credits to end users. Kind regards, Romeo Zwart

10 15