- ripe-atlas - mailman.ripe.net

LLDP / LLDP-MED support?
by Pekka Järvinen 07 Jul '15

07 Jul '15

Hi, Would there be any idea to add LLDP support to probes? -- Pekka Järvinen

3 2

Fwd: Your RIPE Atlas Probe (ID: 22769) is not connected to our network
by Jonathan Brewer 07 Jul '15

07 Jul '15

Hi There, My probe 22769 appears to be malfunctioning, and I'm not sure what to do in terms of diagnostics. >From the router nearest it on the network: https://www.dropbox.com/s/ghe4e3tz69u1kvc/Screenshot%202015-07-07%2011.30.1… Looks to me as if it's rebooting frequently, but I have no way to check without an in-person visit. Do you have any suggestions as to how to troubleshoot? I have access to the network it's on. Thanks, Jon ---------- Forwarded message ---------- From: RIPE Atlas <no-reply(a)ripe.net> Date: 6 July 2015 at 07:40 Subject: Your RIPE Atlas Probe (ID: 22769) is not connected to our network To: jon.brewer(a)gmail.com Dear RIPE Atlas probe host, Thank you for participating in RIPE Atlas! We have noticed that your probe (#22769 with description MDC) is not connected to our infrastructure and has been disconnected since 2015-06-28 22:42 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. You can review the instructions for setting up your probe at https://atlas.ripe.net/getting-started If you have any questions, please contact us at atlas(a)ripe.net Best regards, RIPE Atlas Team ********** You are receiving this message because you applied for or were given a RIPE Atlas probe. We will only send messages when your probe becomes disconnected for an extended period of time.

1 0

API to get information about a probe?
by Stephane Bortzmeyer 06 Jul '15

06 Jul '15

I cannot find an API to retrieve information about a probe. I would like to get the information I can see on, for instance, <https://atlas.ripe.net/probes/10644/> but from a REST + JSON API. Does it exist? Do you think it would be a nice addition? (My current use case is that I find some probes failing to ping a target and I would like to quickly check if they share something, such as ASn or some tags.)

2 3

Wrong IP prefix values accepted?
by Stephane Bortzmeyer 05 Jul '15

05 Jul '15

It seems there is no protection against wrong prefixes? See measurement #1897909, which started with JSON: {'definitions': [{'query_class': 'IN', 'description': 'DNS resolution of jihadmin.com from prefix foobar', 'af': 4, 'query_argument': 'jihadmin.com', 'query_type': 'A', 'type': 'dns', 'is_oneoff': True, 'recursion_desired': True, 'use_probe_resolver': True}], 'probes': [{'requested': 3, 'type': 'prefix', 'value': 'foobar'}]}

2 5

Fwd: [mat-wg] New on RIPE Labs: Improving RIPE Atlas Coverage. What Networks are Missing?
by Robert Kisteleki 02 Jul '15

02 Jul '15

Dear all, The following article might be of interest to you. Regards, Robert -------- Forwarded Message -------- Subject: [mat-wg] New on RIPE Labs: Improving RIPE Atlas Coverage. What Networks are Missing? Date: Thu, 02 Jul 2015 12:18:55 +0200 From: Mirjam Kuehne <mir(a)ripe.net> To: mat-wg(a)ripe.net Dear colleagues, In this article we compare RIPE Atlas deployment against user population estimates provided by APNIC to see what eyeball networks are missing out on RIPE Atlas probes: https://labs.ripe.net/Members/emileaben/improving-ripe-atlas-coverage-what-… Kind regards, Mirjam Kuehne RIPE NCC

1 0

Probe and measurement archives vs. the APIs
by Robert Kisteleki 02 Jul '15

02 Jul '15

Dear All, We've observed recently that some users are using scripts to "crawl" through all the metadata provided by the probe and measurement APIs. This means that some people out there download basically the entire probe and/or measurement meta data set the system provides. As you can imagine, this is highly inefficient and keeps our servers busy. We believe that there could be better solutions. We have been providing the downloadable archive for probe metadata for some time now, and recently we've added the measurement metadata too. You can now reach these at http://ftp.ripe.net/ripe/atlas/ This way one can even get complete sets of metadata as far back as January 2015 for measurement specifications and March 2014 for probe data. Given the existence of these archives, we will apply a sane limit on how much metadata can be reached via the APIs. In practice this means that the API will not allow fetching results beyond, say, 10.000 (i.e. 500 pages of 20) entries. This is after the application of filters, so for example with no filters at all you could still access metadata of the 10k newest measurements, while if you filter for DNS measurements only, you could get the 10k newest of those, and so on. We believe this keeps the metadata API useful for the majority of the users, while the existence of the archive serves the remaining cases. Our plan is to make this change around the end of July. Regards, Robert Kisteleki

1 0

RIPE Atlas traceroute visualisation - use cases
by Massimo Candela 01 Jul '15

01 Jul '15

Hello, We are creating a tool to visualise traceroute results coming from the RIPE Atlas measurement network. The tool will of course be available to everyone. To help make this tool as useful as possible, I’m gathering use cases of day-to-day operations and research activities that use traceroute measurements. I hope you can spend a few minutes to answer this email and tell me how you use traceroute measurements or what you would like to have in such a tool. For each use case you have in mind, please describe it briefly. Keep in mind our system can collect measurements from multiple sources to a single target repeatedly (e.g. every 60 seconds). Don’t focus only on traceroute data, but also on correlations among traceroutes and BGP, RTT, geolocations, DNS, and registry information (feel free to expand the list to other datasets). Thanks for your time. Your help is invaluable. Ciao, Massimo RIPE NCC

2 1

DHIRAAGU (Maldives) has joined RIPE Atlas anchors
by Michela Galante 30 Jun '15

30 Jun '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 mv-mle-as7642 and it is hosted by DHIRAAGU in Male, Maldives, and sponsored by APNIC. 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

Re: [atlas] vm image for ripe atlas probe ?
by Colin Johnston 30 Jun '15

30 Jun '15

low vm disk use is priority low vm memory is priority colin Sent from my iPhone > On 30 Jun 2015, at 11:15, RIPE Atlas <atlas(a)ripe.net> wrote: > >> On 2015-06-22 15:03, Colin Johnston wrote: >> any news on vm image for ripe atlas probe ? >> would be great to use as could monitor vm farms much better ? >> >> Colin. > > Dear all, > > We understand that some people asked for this feature. At the moment we're > evaluating it, and plan to come back to the community with a plan of action > before the end of August. It's possible that we'll post a couple of > clarification questions in the meantime. > > Regards, > Robert

1 0

vm image for ripe atlas probe ?
by Colin Johnston 30 Jun '15

30 Jun '15

any news on vm image for ripe atlas probe ? would be great to use as could monitor vm farms much better ? Colin.

5 4