- ripe-atlas - mailman.ripe.net

Re: [atlas] Timeout on Ping Measurements
by Philip Homburg 15 Jul '13

15 Jul '13

On 2013/07/14 19:35 , Rusty Dekema wrote: > > What is the default timeout on ICMPv4 user-defined measurements made > on RIPE Atlas? I am guessing something like 1.2 s based on > observations, but I'd like to know definitively. It should be 1 second. > Also, is it possible to increase the timeout? One of the targets I > have been measuring often takes a very long time to respond (due to > congestion or link-layer retries) and I would like to have a high (5 > second, perhaps) timeout on these pings. I haven't noticed an option > to set this when setting up the measurement, but it's very possible > I've overlooked something. At the moment there is no option to change the ping timeout. Traceroute does have that option. Philip

1 0

Timeout on Ping Measurements
by Rusty Dekema 14 Jul '13

14 Jul '13

Greetings, What is the default timeout on ICMPv4 user-defined measurements made on RIPE Atlas? I am guessing something like 1.2 s based on observations, but I'd like to know definitively. Also, is it possible to increase the timeout? One of the targets I have been measuring often takes a very long time to respond (due to congestion or link-layer retries) and I would like to have a high (5 second, perhaps) timeout on these pings. I haven't noticed an option to set this when setting up the measurement, but it's very possible I've overlooked something. Cheers, Rusty Dekema

1 0

[iesg-secretary@ietf.org: [lmap] WG Action: Formed Large-Scale Measurement of Broadband Performance (lmap)]
by Stephane Bortzmeyer 11 Jul '13

11 Jul '13

It seems quite close from what Atlas is doing. Atlas documentation in a RFC, one day? :-)

2 1

300 probes just disappeared?
by Stephane Bortzmeyer 11 Jul '13

11 Jul '13

Yesterday, on the Web site, there were > 3400 probes, now: Probes connected to RIPE Atlas: 3177

3 2

atlas.ripe.net website reliability
by Mike. 11 Jul '13

11 Jul '13

About 20% of the time I try to access the website, the browser times out. Granted, I tend to access the website when it is the early morning hours in Europe, perhaos maintenance is being performed. Are there any plans in place to make the website more available to global viewers?

5 6

A Tutorial on Large-Scale Measurement Platforms
by Vaibhav Bajpai 03 Jul '13

03 Jul '13

Hello, We recently gave a tutorial on Large-Scale Measurement Platforms at AIMS 2013 [1]. The tutorial is available at [2]. [1] http://www.aims-conference.org/2013/labs.html [2] http://cnds.eecs.jacobs-university.de/tutorials Abstract: --------- This tutorial provides an introduction into large-scale measurement platforms. It begins by surveying active measurement studies that paved way for the deployment of such platforms. It then describes the internals of the RIPE Atlas and SamKnows platforms, their architecture and surveys the work published from insights discovered from the collected data. The first part concludes by introducing the current Large Scale Measurement of Access Network Performance (LMAP) standardisation efforts in the IETF. The second part of the tutorial provides practical training on how to virtualise an OpenWrt-based Customer Premises Equipment (CPE) and bootstrap it to register as a Measurement Agent (MA) with a controller. The MA is then used to install a measurement test, schedule the reporting of the measurement test results and use a REST API to send and retrieve the measurement results back from the collector. The tutorial also provides training on how to use the RIPE Atlas REST API to create User Defined Measurements (UDMs), and retrieve the UDM measurement results. It concludes with a description of the UDM result data structures and a brief of how programming tools can be used to analyse such data. Best Regards, Vaibhav Bajpai and Nikolay Melnikov About authors: Vaibhav Bajpai is a PhD student at Jacobs University Bremen, Germany. His research focuses on understanding the impact of network infrastructure changes using Large-Scale Measurement Platforms. http://vaibhavbajpai.com Nikolay Melnikov is a PhD student at Jacobs University Bremen, Germany. His research focuses on identification and differentiation of Internet users based on their browsing patterns and behaviors. http://nmelnikov.com

1 0

Mid-summer community update
by Vesna Manojlovic 01 Jul '13

01 Jul '13

Dear RIPE Atlas community, you have been very active recently. I summerized it (ha! pun intended) in the RIPE Labs article, highlighting new community related features for RIPE Atlas anchor hosts, sponsors and "ambassadors". And the article has lots of pretty pictures! Share and enjoy! Warm regards, Vesna https://labs.ripe.net/Members/becha/ripe-atlas-midsummer-2013-community-upd…

1 0

Spam on this list
by Carsten Schiefner 27 Jun '13

27 Jun '13

Dear NCC colleagues, are the first ideas for counter-measures being already floated around internally about how to deal with the (increasing...) amount of spam mails being distributed via this list? Thanks and best: -C.

4 6

[UDM creation API] Which parameters are mandatory?
by Stephane Bortzmeyer 27 Jun '13

27 Jun '13

It seems that in <https://atlas.ripe.net/doc/measurement-creation-api/> (now linked from the Atlas documentation so I assume it is no longer in alpha test), there is no mention of which properties are mandatory and which are not. I have to resort to trial-and-error. For instance, for DNS measurements, the property query_class appear to be mandatory (otherwise, I get an error 400) which is suprising (it defaults to IN in all the DNS clients I know).

2 2

No more a list of probes when the measurement is ongoing?
by Stephane Bortzmeyer 24 Jun '13

24 Jun '13

I relied on a "probes" field in the <https://atlas.ripe.net/api/v1/measurement/1011817/?fields=> data to find out the number of probes allocated to a measurement. Now, it is no longer available :-( % curl 'https://atlas.ripe.net/api/v1/measurement/1011817/?fields=' {"can_visualise": false, "creation_time": 1372080547, "description": "IPv4 base connectivity tests with 46.226.105.0", "dst_addr": "46.226.105.0", "dst_asn": null, "dst_name": "46.226.105.0", "interval": null, "is_oneoff": true, "is_public": true, "msm_id": 1011817, "packets": 3, "probe_sources": [["Area", "WW", 10]], "resolve_on_probe": false, "resolved_ips": ["46.226.105.0"], "result": "/api/v1/measurement/1011817/result/", "start_time": 1372080547, "status": {"id": 2, "name": "Ongoing"}, "stop_time": null, "type": {"id": 1, "name": "ping"}} What is its replacement?

2 2