- ripe-atlas - mailman.ripe.net

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

Huge credit debit
by Mike. 12 Oct '13

12 Oct '13

One of my measurements (that usually uses about 1000 credits per day) all of a sudden posted a credit usage of 2,293,788.00 credits for a single measurement. 2013-10-10 18:13 UTC UDM 764596 samples of msm #1013277 -2,293,788.00 -1,279,520.00 I don't know where or why the 764596 samples came from, usually only 90 samples are performed. Was there a proble in the measurement or credit system recently? Thanks.

3 6

Problems with one-off measurements
by Robert Kisteleki 07 Oct '13

07 Oct '13

Dear RIPE Atlas users, It has come to our attention that one-off measurements at the moment don't produce the expected number of results. So far our investigation shows that this is most likely a probe firmware issue. We'll let you know once we find the real cause and have a fix for this. In the meantime please accept our apologies for the reduced usefulness of this function. Regards, Robert Kisteleki for the RIPE Atlas team

1 1

Question about rt definition of DNS measurements
by Klaus Darilion 06 Oct '13

06 Oct '13

Hi! When doing DNS measurements I see that the average "rt" time is considerable higher when setting the DO bit. When I check my name servers manually with dig (with and without DO) I do not see any considerable differences. Thus, I wonder how "rt" is measured in the Atlas probes and if the probe does some DNS/DNSSEC relevant processing during the "rt" interval, or is it really just the time between sending and receiving of the packets on IP layer? Thanks Klaus

2 1

Announcing RIPE Atlas Service Terms Documentation for Anchor Hosts
by Vesna Manojlovic 03 Oct '13

03 Oct '13

Dear colleagues, In the process of transitioning RIPE Atlas anchors towards being a production service, we have developed two documents that describe the service terms: - Draft RIPE Atlas Service Terms and Conditions - Memorandum of Understanding - Hosting a RIPE Atlas Anchor Probe Please see the details in this RIPE Labs article: https://labs.ripe.net/Members/becha/ripe-atlas-anchors-terms-and-conditions If you are currently hosting an anchor, or if you are interested in hosting a RIPE Atlas anchor in the future, we would like to hear any feedback you have on these draft documents. Our goal is to finalise the documents by 11 October so that we can announce the production service at the upcoming RIPE 67 Meeting in Athens. Regards, Vesna -- Vesna Manojlovic BECHA(a)ripe.net Senior Community Builder @Ms_Measurements for Measurements Tools RIPE NCC http://ripe.net

1 0