July 2013 - ripe-atlas - mailman.ripe.net

Atlas F.ROOT ping
by Peter Gervai 09 Jan '14

09 Jan '14

Hello, Atlas helped me today first to see a hard-to-detect bug: F-root anycast algo works fine for v4 but fails miserably for v6, as instead of AMSterdam it sends all traffic to some remote island in the pacific. ;-) Seems to be the reverse true for M-root: ipv4 sends me off to nowhere land while v6 is great. A-root follows the F-suit. (C-root is not a good avertisement valie for Cogent, with v4 only address and considerable ongoing pkt loss.) Thanks! Peter

4 5

RIPE Atlas maintenance on Tuesday, 6 August
by Robert Kisteleki 06 Aug '13

06 Aug '13

Dear RIPE Atlas users, We'd like to let you know that we plan to perform scheduled maintenance on the RIPE Atlas central infrastructure on Tuesday, 6 August, for a couple of hours during the day. In this period, main features including the RIPE Atlas user interface (atlas.ripe.net) data downloads and measurement scheduling functions will be unavailable. Probes will continue to work and all results will still be collected or buffered; however, during the maintenance period you will be unable to log in to the website, manage your probes/measurements, or get to result data/visualisations. We apologise for any inconvenience this may cause. Regards, Robert Kisteleki

1 1

Registering a new probe...
by Chris Elliott 31 Jul '13

31 Jul '13

I have one probe (3690), and just received two new probes from Nathalie Trenaman, thanks to Bert Wijnen. However, either I'm just flat out missing something or the registration page is broken. I go here: https://atlas.ripe.net/register/ I ensure I'm logged in, and try to complete the registration process. No matter what, it always says: - There were some problems with your submission. Please see below However, nothing is highlighted or otherwise called out as an issue. I've tried various combinations in various fields, with no success. Here's one of the settings I've tried: - On what sort of network will you be installing the probe? * Residential/Consumer Business Network Educational Network IXP RIPE NCC Member (LIR) - Organisation Name * - What's the connection speed like on that network? * < 1 Mb/s 1-4 Mb/s 5-9 Mb/s 10-19 Mb/s 20-49 Mb/s 50-99 Mb/s 100-499 Mb/s 500-999 Mb/s > 1 Gb/s I don't know - AS Number - My network supports IPv4 - IPv4 Network Prefix - Please enter a valid prefix. - My network supports IPv6 - IPv6 Network Prefix - How did you receive your probe? * From conference/training From sponsor Other - Who is the sponsor? * - MAC Address - Location * <http://maps.google.com/maps?ll=21.351893,-102.718887&z=2&t=m&hl=en-US&mapcl…> Map data ©2013 MapLink - Terms of Use<http://www.google.com/intl/en-US_US/help/terms_maps.html> Map Satellite - I'm willing to keep the probe online 24/7 - I'm willing to make my probe visible to the public - I accept the rules of the game a.k.a. Pilot Service Rules<https://atlas.ripe.net/service-rules/> * Thanks for looking into this issue. Chris. -- Chris Elliott chelliot(a)pobox.com

2 2

HTTP or not HTTP?
by Stephane Bortzmeyer 31 Jul '13

31 Jul '13

I'm surprised to see in UDM documentation that you can do HTTP measurements: https://atlas.ripe.net/doc/udm#http-http6 But I do not find this option in the "Choose a measurement" menu of the Web interface. And it is not documented in the REST API: https://atlas.ripe.net/doc/measurement-creation-api/ > type: One of ping,traceroute,dns or sslcert So, can we do HTTP measurements with the Atlas probes?

2 3

Outdated documentation to delete
by Stephane Bortzmeyer 30 Jul '13

30 Jul '13

IMHO, the "mechanize" example in <https://atlas.ripe.net/doc/code#access_from_scripts> is useless now that we have an API and should be deleted.

1 0

Spoofing the source IP address from a probe?
by Stephane Bortzmeyer 30 Jul '13

30 Jul '13

I read in the interesting <http://www.internetsociety.org/blog/2013/06/can-we-stop-ip-spoofing-internet> about BCP38 (anti-spoofing): > Another possibility that was suggested is using RIPE Atlas probes to > probe network capabilities (or shall we say incapabilities?). AFAIK, Atlas probes cannot currently perform these tests, am I correct?

9 11

Re: [atlas] Spoofing the source IP address from a probe?
by Alex Saroyan 30 Jul '13

30 Jul '13

Hi, Probably we don't need to spoof all address space, instead only if spoofing enabled just spoof to some predefined address range. Regards. /Alex Sanjeev Gupta <ghane0(a)gmail.com> wrote: >On Tue, Jul 30, 2013 at 11:22 AM, Randy Bush <randy(a)psg.com> wrote: > >> I support this point of view. I think controlled (anti-)spoofing >> measurements performed by the RIPE NCC with the consent of >> participating probes would be a good service to the community. > >perhaps the probe owners are not the only parties with skin in the game >and whose consent would be relevant? > > >Exactly. I host probes, and since you are spoofing others, we need to ask them. > >How you do this is left as an exercise to the reader. > >-- >Sanjeev Gupta >+65 98551208 http://www.linkedin.com/in/ghane > > >

1 0

Re: [atlas] Outdated for more than one day?
by Fred Grayson 28 Jul '13

28 Jul '13

Hello, The probe ID is 10156. It is attached to a third interface on my router. The graphs have been stalled for the last four days. The probe went online on June 26 and all was well until this happened on July 24. Thanks for looking. FG On 7/28/2013 6:35 AM, Iñigo Ortiz de Urbina wrote: > Good morning Fred, > > I just took a minute to check what you shared with the list. > > My two probes and built-in measurements look just fine (i.e they are > up to date). Your issue may be a temporary error. However, if you'd > like more details on your particular probe/problem pair, I've found it > to be helpful to provide details, such as probe ID or which controller > it is attached to. > > Are you still seeing the same stalled graphs? > > Regards, > > On Sat, Jul 27, 2013 at 8:53 PM, Fred Grayson <fred_grayson(a)yahoo.com> wrote: >> Hello, >> >> Recently, all Built-in-Measurments for my probe began showing "Outdated for >> more than one day" and none of the graphs are current, most show some white >> space at the far right hand side. >> >> My Total Uptime: 99.56% (31d, 22h, 30m) and I have power cycled the device >> twice trying to solve the problem. >> >> Any ideas on how to fix this will be appreciated. >> >> Thanks, >> >> FG >> > > >

1 0

Outdated for more than one day?
by Fred Grayson 27 Jul '13

27 Jul '13

Hello, Recently, all Built-in-Measurments for my probe began showing "Outdated for more than one day" and none of the graphs are current, most show some white space at the far right hand side. My Total Uptime: 99.56% (31d, 22h, 30m) and I have power cycled the device twice trying to solve the problem. Any ideas on how to fix this will be appreciated. Thanks, FG

1 0

Ping Fails (ns.ripe.net)
by AlbyVA 23 Jul '13

23 Jul '13

In reviewing My Probe stats, it appears that (ns.ripe.net) was once able to ping the server, but now it appears to be failing. All my other ping stats under My Probe show successful pings to other servers, but for some reason ns.ripe.net is failing. Does anybody have a suggestion of what might be going on, since ping is working to all the other servers. -Alby

4 6

No address in the results when ping or traceroute fail?
by Stephane Bortzmeyer 23 Jul '13

23 Jul '13

When a ping or traceroute emasurement fails, we do not know the IP address of the probe (empty "from" and no "src_addr"), which is annoying when you want to analyze the possible causes of the failure: { "size": 20, "addr": "2620:0:2d0:200:0:0:0:7", "min": -1, "rcvd": 0, "from": "", "dst_name": "2620:0:2d0:200:0:0:0:7", "af": 6, "timestamp": 1374395985, "fw": 4520, "proto": "ICMP", "name": "www.icann.org", "prb_id": 3953, "result": [ { "error": "sendto failed: Network is unreachable" }, { "error": "sendto failed: Network is unreachable" }, { "error": "sendto failed: Network is unreachable" } ], "max": -1, "dup": 0, "avg": -1, "type": "ping", "dst_addr": "2620:0:2d0:200::7", "sent": 0, "msm_id": 1013576 },

3 6

No probe shown in My Probes list (Registered. Plugged Probe v3 to network. 1st, 3rd, 4th LEDs lighted up.)
by Arthit Suriyawongkul 22 Jul '13

22 Jul '13

Hi I'm Arthit from Bangkok. New here. The switch at the probe is now at "3G/4G". Should i change to WISP or AP? thanks, Art -- เครือข่ายพลเมืองเน็ต -- "เปิดเน็ต เปิดใจ" Thai Netizen Network -- "Open Net. Open Mind." https://www.facebook.com/thainetizen

3 4

Strange and undocumented (?) result in traceroute JSON output
by Stephane Bortzmeyer 17 Jul '13

17 Jul '13

Measurement #1013405 contains: "result": [ { "x": "*" }, { "late": 20, "ttl": 61, "from": "88.79.15.141", "size": 96 }, { "x": "*" }, { "x": "*" } While "late" is documented <https://atlas.ripe.net/doc/data_struct#v4400_traceroute>, the lack of "rtt" field is not and crashes tools like json2traceroute.py.

3 2

[UDM] What value to give to 'requested' when 'type' = 'msm'?
by Stephane Bortzmeyer 17 Jul '13

17 Jul '13

The documentation <https://atlas.ripe.net/doc/measurement-creation-api/> says: "probes": [ { "requested": 1, "type": "msm", "value": 1000002 } ] but, from my tests, if you do so, you get only one probe, whatever measurement #1000002 actually used. To get all the probes, I had to indicate a very large number in 'requested' (unless you remember or count the actual number).

2 2

IPv6 and Atlas probe v3
by Mike. 16 Jul '13

16 Jul '13

My probe works fine on IPv4, obtaining IP address, router, and DNS servers via DCHP. The IPv6 capability has me curious with two questions... I statically configured the IPv6 address via the web interface. I gave the probe an IPv6 address from my prefix, a gateway address, and the IP address of a DNS recursive server provided by my tunnel vendor. The IPv6 address shows up OK on the web interface ("Internet Address") The AS Number also shows up fine. The Gateway is "Undetermined/Unknown" The IP addr of the DNS server is listed as shown below. In the text table below the configuration info, I see: ("V" is a check, "X" is an X) Static Enabled Probe Knows Probe Uses Last Static Address Given IPv6 V V V 2001:470:xxx:xxx::xxx DNS V V X 2001:470:20::2 Question #1: Why is there an "X" for DNS in the "Probe Uses" column? Is there something wrong with that DNS server? When I query DNS from another box on the same subnet as the Atlas probe I get valid results: ; <<>> DiG 9.8.3-P4 <<>> @2001:470:20::2 atlas.ripe.net any ; (1 server found) ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 19739 ;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 0 ;; QUESTION SECTION: ;atlas.ripe.net. IN ANY ;; ANSWER SECTION: atlas.ripe.net. 5922 IN AAAA 2a01:4f8:121:30a3::78:16 atlas.ripe.net. 5911 IN A 178.63.78.16 ;; Query time: 21 msec ;; SERVER: 2001:470:20::2#53(2001:470:20::2) ;; WHEN: Mon Jul 8 12:24:01 2013 ;; MSG SIZE rcvd: 76 I also noticed this sentence at the bottom of the https://atlas.ripe.net/doc/static-config page: "...As of now, we have no way of preventing the probe from accepting RAs. So if there is an IPv6 (rogue) RA on you network, it can/will override part of the static configuration. We're unsure if this will change in the future. ..." I do have RA support on the subnet, though I would not classify it as "rogue". :) The RA provides the IPv6 prefix, prefix length, and the IPv6 address of the recursive DNS server. This RA support has been used by another box on the subnet, and it seems to work fine. Question #2: Does the Atlas v3 probe use RA if they are present? Thanks.

2 2

Just to say thank you
by Stephane Bortzmeyer 16 Jul '13

16 Jul '13

With Atlas probes, we were able (at the cost of a few credits) to solve a difficult network connectivity problem. I just wanted to say THANKS.

1 0

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