- ripe-atlas - mailman.ripe.net

What is the Aggregator on Map of DNS Measurements
by Klaus Darilion 09 Dec '15

09 Dec '15

Hi! The MAP of DNS Measurements contains an "Aggregator" option. Unfortunately the online help (Enter a regular expression ....) does not help much. Is this feature somewhere described in detail? I do not understand it. Thanks Klaus

2 2

CAIDA BGP Hackathon 6-7 Feb 2016 -- Call for Participation
by Vesna Manojlovic 09 Dec '15

09 Dec '15

Hi everyone, as a continuation of our own successful RIPE Atlas events, we are now taking part in CAIDA's BGP "live" hackahton, by providing data, measurements platform, expertise -- and you ;-) RIPE NCC's services, such as RIS & RIPE Atlas, will be "remixed" with other BGP-related data sources & tools, to create wonderful new hacks. As participants in RIPE Atlas community, you are very much invited to take part in this event. Details are below. Regards, Vesna -------- Forwarded Message -------- Subject: [mat-wg] CAIDA BGP Hackathon 6, 7 Feb 2016 -- Call for Participation Date: Tue, 8 Dec 2015 20:37:49 -0800 From: Alberto Dainotti <alberto(a)caida.org> To: mat-wg(a)ripe.net What: CAIDA BGP Hackathon, Call for Participation (CFP) When: Feb 6-7, 2016 Where: the San Diego Supercomputer Center (SDSC) on the University of California at San Diego (UCSD) campus. Who: Parties interested in hacking on live BGP data. Inquiries: bgp-hackathon-info(a)caida.org Important Deadline: Dec 22, 2015 for travel grant requests Apply to attend: http://www.caida.org/workshops/bgp-hackathon/1602/ CAIDA, in cooperation with CSU, USC, UFMG, FORTH, Route Views, RIPE NCC, will host a BGP Hackathon on the 6-7th of February 2016 at UC San Diego (La Jolla, CA, USA). The theme of the hackathon is “live BGP measurements and monitoring”. We will provide participating teams with access to data sources and a toolbox: live streaming of BGP data, the new BGPMon interface, BGP processing tools and APIs such as the opensource BGPStream software framework, the PEERING testbed, RIPE RIS, visualization tools, and data-plane active measurement platforms such as CAIDA Ark and RIPE Atlas. Participating teams will work on "challenges" that extend, integrate and demonstrate the utility of these platforms/data for understanding or solving practical problems (e.g., detecting BGP prefix hijacking, evaluating anycast performance, effectively visualizing phenomena). The hackathon will be held in San Diego the weekend immediately preceding the NANOG conference and the AIMS academic Internet measurement workshop. The hackathon aims to: - bring together these different communities, e.g., to discuss problems operators face that academics may want to research; - advertise tools (e.g., PEERING peering.usc.edu, BGPStream bgpstream.caida.org) to the communities and get people familiar with using them, and encourage further use in the future; - get people working together on interesting/important problems, hopefully spurring further collaboration on these problems; - provide extra incentive for students to attend NANOG. ### FORMAT Each team of 2-4 people will work on a "challenge". The organization committee will propose a set of challenges to bootstrap feedback and refinement based on community input: participants can propose totally new challenges, modifications to existing ones, and express their preferences. The set of potential challenges is described in the event website at https://github.com/CAIDA/bgp-hackathon/wiki/List-of-Challenges and will continuously evolve in the days preceding the hackathon. On Saturday morning, participants will very briefly introduce their interests and ideas and teams will be officially formed. On Saturday and Sunday, participants will work together in teams to hack and develop their ideas, culminating in very short presentations to the jury on Sunday evening and a party to announce the winning teams and celebrate everyone's participation. During the event, domain-experts will provide support to the teams. Participants are free to work on drafted challenges and on their own ideas in the days preceding the hackathon. A mailing list and documentation will provide support on the platforms/tools/data used in the hackathon. However, for the teams to compete in the hackathon for prizes, they will have to demonstrate that substantial work was done during the two-day event. ### PARTICIPATION AND TRAVEL GRANTS Application to participate in the hackathon is open from December 8, 2016. Application does not guarantee participation. There is no application fee, and no participation fee. We will accept applications until one week before the hackathon, or until capacity is reached. However, the deadline to apply for a travel grant (through the hackathon application form) is 22 December 2015. Travel grants reimburse flights and hotel expenses. Food and drinks will be provided throughout the two-day event. http://www.caida.org/workshops/bgp-hackathon/1602/

1 0

Map-based visualisations for Atlas data
by Baptiste Jonglez 08 Dec '15

08 Dec '15

Hi, Is there a way to reuse and adapt the code for the maps available here? https://atlas.ripe.net/results/maps/ It could be interesting to have a generic map-based visualisation, where all probes matching a certain set of conditions would be displayed. Possible applications include: - monitor IPv6 deployment for an AS, by displaying all probes matching "asn_v6 = XX". It would probably be useful to also display probes matching "asn_v4 = XX", as a baseline, using a different color - monitor DNS resolver outage geographically, by matching on system tags like "resolving A doesn't work". - match on user tags, like "IXP" or "core", to monitor deployment of Atlas at specific locations/types of networks. In all those examples, the "time slider" functionality would be extremely useful, to see the evolution over time. It could be even nicer if the slider could move automatically, so as to provide nice animations. Is all this currently feasible, and if not, would it be hard to implement? Thanks, Baptiste

3 2

Turris Omnia as probe Platform?
by Kessler, Thomas 08 Dec '15

08 Dec '15

Dear all, some of you are probably aware of the Turris Omnia project by CZ.NIC ( https://www.indiegogo.com/projects/turris-omnia-hi-performance-open-source-… ). This might be an interesting platform for running an VM probe?! Just thought it might be worth brining it up here for discussion. Cheers Thomas

7 9

New on RIPE Labs: DomainMON in RIPE Atlas
by Chris Amin 07 Dec '15

07 Dec '15

Dear colleagues, A few weeks ago we gave you a heads up about a new visualisation tool in RIPE Atlas called DomainMON, and we're pleased to announce that this is now available for all RIPE Atlas users with available credits. Please find more details on RIPE Labs: https://labs.ripe.net/Members/suzanne_taylor_muzzin/ripe-atlas-domainmon-is… Kind regards, Chris Amin RIPE NCC

1 1

Probe power down.
by Alistair Mackenzie 07 Dec '15

07 Dec '15

Hi all, I'm currently moving house and expect my probe to be offline for approximately one week, Is there any formal channels that I must notify ripe of this other than the location change once it's back online? Thanks, Alistair

3 3

Dead probes
by Marty Strong 01 Dec '15

01 Dec '15

Hi, I've got 1 or 2 dead probes, they power on but I see no mac address from them. They have the first 2 lights on, but none of the others. I don't see this combination listed on https://atlas.ripe.net/about/faq/#what-do-the-lights-on-the-side-of-the-pro… Has anybody else come across this issue? Anybody know what the light combination means? Marty

9 15

location field in probe API
by Bajpai, Vaibhav 01 Dec '15

01 Dec '15

Hello, TL;DR: The probe API does not expose the probe location even if I explicitly ask for it. location: A human readable location for this probe, either explicitly specified by the probe owner, or derived from the longitude and latitude. It appears the 'location' field in the probe API is hidden by default and it must be explicitly set in the request parameters to expose location field values. However, even if I do set it, I still don't get location entries. I made multiple permutations of query requests and also tried the usage example on the API documentation webpage [1]: Get the IPv4 addresses and the usually hidden human readable location string for public probes in Germany: https://atlas.ripe.net/api/v1/probe/?country_code=de&is_public=true&fields=… What could be wrong? -- Thanks! PS: It seems, this field is also missing in the probe archive API. [1] https://atlas.ripe.net/docs/rest/#probe Best, Vaibhav ===================================================== Vaibhav Bajpai Room 91, Research I School of Engineering and Sciences Jacobs University Bremen, Germany www.vaibhavbajpai.com =====================================================

1 0

Fwd: Re: Measurements delete and ping issue
by Daniel Karrenberg 30 Nov '15

30 Nov '15

I did not copy the list on this message and then realised that it is a generic answer that deserves to be seen and archived here. Daniel -------- Forwarded Message -------- Subject: Re: [atlas] Measurements delete and ping issue To: Andrea Consadori <andrea.consadori(a)hotmail.it> References: <DUB126-W888F5B62064D1CE913A99DE0000(a)phx.gbl> From: Daniel Karrenberg <daniel.karrenberg(a)ripe.net> Message-ID: <565C9760.2050704(a)ripe.net> Date: Mon, 30 Nov 2015 19:37:20 +0100 On 30.11.15 15:42 , Andrea Consadori wrote: > > > Hi all, > i just start using proble atlas and i found is not possible to delete > Stopped measurements from web, it's normal? > i try to search on old mailing list messages and seems to be and old > issue but i still cannot delete stopped masurements > (for example ids: 3050379 > <https://atlas.ripe.net/measurements/3050379/>, 3034900 > <https://atlas.ripe.net/measurements/3034900/>) > ... Andrea, An important idea behind RIPE Atlas is that all results are re-useable. Therefore we store the results of *all* measurements as long as we possibly can because those results can be useful for other researchers even if they did not run the measurements themselves. Each result says something about the packet flow in the Internet at the particular time it was obtained. There is no way we can foresee how these results can help to answer interesting research questions and help us to understand the Internet packet layer better than we do now. For a recent example of this, please see https://labs.ripe.net/Members/becha/ripe-atlas-tools-hackathon-results "ASN Tryst". Therefore we do not provide the functionality of deleting measurements. The only way we foresee that results can be deleted is if we run out of storage space. Of course that one has to be careful to select the measurements one wants to re-use according to the question one wants to answer. Your measurement shows this very well. I do not recommend using your results unless the question is about reachability with RTTs under 6ms. I hope this answers your question Daniel (co-inventor of RIPE Atlas)

1 0

Measurements delete and ping issue
by Andrea Consadori 30 Nov '15

30 Nov '15

Hi all, i just start using proble atlas and i found is not possible to delete Stopped measurements from web, it's normal? i try to search on old mailing list messages and seems to be and old issue but i still cannot delete stopped masurements (for example ids: 3050379, 3034900) Another issue i see, if i create a ping measurement (id 3034899) under probes i see RTT column unreachable for every raw... but the public ip is pingable form everywhere.. maybe there's simple solutions i cannot found, if so can someone show me a good link where to found how to fix this two issues? Regards Andrea Consadori

2 1