- ripe-atlas - mailman.ripe.net

Bulk access to the measurements?
by Stephane Bortzmeyer 13 Nov '13

13 Nov '13

A colleague asks me if it is possible to have bulk access to public measurement data. (Properly: otherwise, he could dor a for loop over all measurement IDs but I suspect it is not nice.) I find nothing in the Atlas documentation. Is it because I do not search hard enough or because this possibility does not exist? #BigData

4 3

Archiving user-defined measurements in Atlas
by ivo.vdmaagdenberg＠gmail.com 12 Nov '13

12 Nov '13

Hi, Played a bit with measurements, now I want make some sensible ones and get rid of the rest. In the documentation "How do I stop a user-defined measurement?" there is mention of the 'Archive' option per measurement. I see that option but it is grayed out. The question is: What are the circumstance that grey the option? This holds for the "Forced to Stop", "Stopped" and "Ongoing" UDMs (maybe more...) Kind regards, Ivo

2 1

Feature request: Regularly Publish Names
by Daniel Karrenberg 12 Nov '13

12 Nov '13

Title: Regularly Publish Names Description: Regularly collect all IP addresses referenced in measurement definitions and all results. Reverse resolve the addresses in the DNS. Collect netnames for the addresses from the RIR registration data. Possibly collect other data such as geo-location and ASes announcing. Publish this collected data both in bulk and thru the API indexed by IP. A frequency of once every 24 hours would be sufficient to stat with. Use: When analysing measurements from the past it is important to have meta information that was current at the time of the measurement. Having this data collected in advance often also allows for more efficient analysis and more responsive tools. Perceived complexity: Low. Use hadoop to collect the list of IPs. Then run a low priority job to collect the meta data. The job also has high potential for parallelism. Perceived cost: Low. Just some cycles and storage on the back end.

1 0

need higher timeout value for ping
by Dave . 08 Nov '13

08 Nov '13

Hi, I did send a mail to atlas(a)ripe.nl. I never received an answer although it's 19 days ago. Not sure if staff is reading here, but let's see. This graph shows pings to a mobile device. A device connected to a mobile network. As mobile networks need to do paging and need some time to re-establish the radio connection, more time is needed for the packets in the first 2 or 3 seconds to get through. My request is to consider making a configurable timeout value for pings? For mobile networks a typical RTT for a first packet would be some 3 seconds. There are however buffers in a typical mobile network which store packets up to 30 seconds in case multiple pagings would fail. I really would like to be able to have a timeout maximum of just over 30 seconds but I could understand if you would limit on 5 seconds. Below, I kept a continuous ping open parallel to the Atlas tests in the marked timeframe. Therefore no paging was needed as the radio channel was kept open all the time. It seems the current timeout is 2 or 3 seconds. Regards, Dave Boonstra. [image: Inline afbeelding 1]

3 3

News about RIPE Atlas anchoring measurements
by Vesna Manojlovic 07 Nov '13

07 Nov '13

Dear colleagues, at the RIPE67 we announced that RIPE Atlas anchors are now ready for the next stage -- full production service. Since then, we already got 10 applications! Currently there are 15 anchors deployed, there is a full-mesh of measurements between the anchors, and we are scaling up the "anchoring" measurements from hundreds of probes towards each anchor, to provide the map of regional reachability. We are now looking for more interested hosts, in new locations. Please find out more details of the benefits of hosting an anchor, technical requirements and available features in RIPE Labs article: https://labs.ripe.net/Members/suzanne_taylor_muzzin/announcing-the-ripe-atl… Regards, Vesna

1 0

msm_name in DNS measurements?
by Gilles Massen 07 Nov '13

07 Nov '13

Hello, I just stumbled over a field 'msm_name' in a DNS UDM - but it's apparently undocumented (at https://atlas.ripe.net/doc/data_struct#v4540_dns ). What could it contain (except 'Tdig')? (and would it be possible to add it to the documentation?) best, Gilles -- Fondation RESTENA - DNS-LU 6, rue Coudenhove-Kalergi L-1359 Luxembourg tel: (+352) 424409 fax: (+352) 422473

4 5

Discussing IPv6 extension headers feature on mat-wg
by Vesna Manojlovic 06 Nov '13

06 Nov '13

Hi RIPE-Atlas-users, one of the features often requested to add to RIPE Atlas is "enable IPv6 extension headers". We would like to know the details of your needs, so please join the discussion on the MAT-WG that Jens started: https://www.ripe.net/ripe/mail/archives/mat-wg/2013-November/000364.html (I am deliberately not copying the text here, please keep the discussion on one list...) Thank you for your input! Vesna

1 0

Fwd: UDM/Credit troubles
by Alex Saroyan 01 Nov '13

01 Nov '13

Hi, I faced some troubles today using Atlas. My running credit consumption was 0 because all UDMs were stopped already for few days(screenshot attached). I have defined 2 UDMs (16 Pings from 12 Probes - nothing special - nothing big - about 300 credits) - they failed to start with no reason (screenshot attached). When defining 3-rd similar UDM, I've got message saying my current consumption is 276800 and no credit available to start an 300 credit UDM.(screenshot attached) It seems to me that some UDM is stuck, it is stopped but Atlas credit system thinks that it is running. So I faced two troubles 1-st regarding mysterious failed UDM and 2-nd regarding credit consumption. -- Regards. /Alex Saroyan

1 1

Replacing "ping RRDs" with "zoomable ping graphs"
by Robert Kisteleki 30 Oct '13

30 Oct '13

Dear RIPE Atlas users, As you may have read in the recent RIPE Labs article (https://labs.ripe.net/Members/becha/seismograph-and-other-new-ripe-atlas-fe…), we've replaced the old style, RRD based visualisation for built-in ping measurements with client side, zoomable graphs. Since then we've also changed the graphs that represent the probe's bandwidth usage. The new graphs have the benefit that they retain all details, even for longer time intervals. (These details were lost in the RRD based graphs over time.) Other reasons why we changed include that generating the RRD graphs did not scale well with the increasing number of RIPE Atlas probes, and making them required us to maintain a large set of backend servers, each being a single point of failure. With the new approach you still have visualisations for this information, with more details and interactivity (though it does require running JavaScript on the client side). We'll change the remaining RRDs to this new model as well in the coming period, and stop generating the RRD based images altogether. We expect to stop with the "built-in pings" and the probe traffic RRDs first, likely in the second week of October. If you would like to embed these new style visualisations into your pages (maybe because you used the RRD graphs before), then you'll have to embed a RIPEstat widget; see https://stat.ripe.net/widgets/demo/atlas_probe_widgets.html for details. Regards, Robert Kisteleki for the RIPE Atlas team

1 1

Strong doubts about the option "DNS recursion"
by Stephane Bortzmeyer 28 Oct '13

28 Oct '13

I fear that the option "recursion_desired" <https://atlas.ripe.net/doc/measurement-creation-api/> does not work as expected. Here was my experiment. I registered a new domain name which never appeared before, d7b16b2a97627e8ccbcccf93e773ec3f.cosmogol.fr. Because of its unreadability, there is zero chance it has ever been in a DNS cache. I then ask Atlas probes to dig it, with "recursion_desired" set to false: {'definitions': [{'query_class': 'IN', 'use_probe_resolver': True, 'af': 4, 'query_argument': 'd7b16b2a97627e8ccbcccf93e773ec3f.cosmogol.fr', 'query_type': 'TXT', 'type': 'dns', 'is_oneoff': True, 'recursion_desired': False, 'description': 'DNS resolution of d7b16b2a97627e8ccbcccf93e773ec3f.cosmogol.fr'}], 'probes': [{'requested': 10, 'type': 'area', 'value': 'WW'}]} But all the probes got the content of this TXT record! Measurement #1034372 if you want to check (unfortunately, this parameter is not displayed in <https://atlas.ripe.net/atlas/udm.html?msm_id=1034372>). It seems wrong, they should all have retrieved an empty answer (here, with dig, the behaviour I expected): % dig +norecurse @MYSERVER TXT d7b16b2a97627e8ccbcccf93e773ec3f.cosmogol.fr ; <<>> DiG 9.8.4-rpz2+rl005.12-P1 <<>> +norecurse @relay1 TXT d7b16b2a97627e8ccbcccf93e773ec3f.cosmogol.fr ; (2 servers found) ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 33141 ;; flags: qr ra ad; QUERY: 1, ANSWER: 0, AUTHORITY: 8, ADDITIONAL: 21 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags: do; udp: 4096 ;; QUESTION SECTION: ;d7b16b2a97627e8ccbcccf93e773ec3f.cosmogol.fr. IN TXT ;; AUTHORITY SECTION: fr. 165392 IN NS d.ext.nic.fr. fr. 165392 IN NS d.nic.fr. ...

4 11