February 2014 - ripe-atlas - mailman.ripe.net

New on RIPE Labs: Improved RIPE Atlas Probe Pages
by Mirjam Kuehne 13 Mar '14

13 Mar '14

Dear colleagues, We've made it easier to get an overview of the history and measurements for all the public probes in the RIPE Atlas network. Read about that and other new functionality on RIPE Labs: https://labs.ripe.net/Members/suzanne_taylor_muzzin/ripe-atlas-improved-pro… Kind regards, Mirjam Kuehne RIPE NCC

5 4

AusRegistry (AU) has joined RIPE Atlas anchors
by Michela Galante 05 Mar '14

05 Mar '14

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 au-mel-as38796 and it is hosted by AusRegistry in Melbourne, Australia. Congratulations to AusRegistry! This is the first anchor in Oceania and the second in the Asia and Pacific area. 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, Measurements Community Building Team RIPE NCC mcb(a)ripe.net

2 1

New on RIPE Labs: The Seismograph User Guide
by Suzanne Taylor Muzzin 05 Mar '14

05 Mar '14

Dear colleagues, Please find a new article on RIPE Labs that explains how you can get the most out of the Seismograph, an interactive RIPE Atlas tool that provides an overview of different RTT and packet loss trends measured by multiple probes. The Seismograph User Guide https://labs.ripe.net/Members/massimo_candela/seismograph-user-guide Kind regards, Suzanne Taylor Muzzin Measurements Community Building RIPE NCC

2 1

Some Atlas Anchor Graphs
by Daniel Karrenberg 27 Feb '14

27 Feb '14

During some research I happened to visualise some random anchor calibration measurements and thought I'd share the graphs. The basis are IPv4 traceroutes from all (4500+) RIPE Atlas probes to the anchor encoded in the file name. The graphs show adjacencies that appear in more than 3% of all paths. IP addresses are aggregated by the network name as registered in the RIR registries. The darker an edge appears, tho more paths contain this adjacency; the colouring is scaled logarithmically. Enjoy Daniel

1 0

Network configuration / Multiple VLANs
by Guillaume Sachot 27 Feb '14

27 Feb '14

Hi, I have just received my Atlas probe, and I have an issue for the IPv6 part. Its definitive IPv4 public address does not share the same VLAN with the IPv6 subnet. Would it be possible to add an optional VLAN field in the network configuration? Thank you, Regards. -- Guillaume SACHOT Oceanet Technology Administrateur système et réseau Support : +332 28 07 14 88

6 13

Thoughts on allowing newer DNS RR queries?
by Mark Delany 21 Feb '14

21 Feb '14

Outside of Atlas I've been doing a few tests to see how well CPE supports newer RR types. By newer I mean newer than AAAA. I'd like to do the same with the Atlas probes. Has there been discussion about being able to issue RR queries of newer types? On the query side, the Atlas device only needs to know enough to encode the type-value which could be supplied as a numeric if necessary. On the response side, a simple hex dump of the response would be good enough. I guess it's sort of a one-off test for most probes because once we know a probe and its intervening caches does or does not support a number of newer types, that situation is unlikely to require re-testing very often. So an alternative might be to make it a bootstrap sequence that the probe goes thru? Out of curiousity, how does the probe do the current DNS queries? Is it via dig or similar or is it coded into a program of some sort? Mark.

5 5

Easier access to bandwidth data of RIPE Atlas anchors
by Vesna Manojlovic 20 Feb '14

20 Feb '14

Dear RIPE Atlas community, we have added a small feature to the listing of RIPE Atlas anchors: https://atlas.ripe.net/anchors/list/ If you click on the hostname of the anchor (e.g. nl-ams-as3333), the link will take you to the graph of bandwidth, served by RIPEstat: https://stat.ripe.net/m/widget/atlas-probe-traffic#w.probe_id=6001&w.measur… This is the same graph that appears on the RIPE Atlas "probe page" of every anchor, but we decided to add a direct link to the bandwidth graph rather then to the whole probe page, since we are working on the improved version of it. The graph is zoomable, so you can see the whole year of data for older anchors; and it has other features described in this RIPE Labs article: https://labs.ripe.net/Members/becha/seismograph-and-other-new-ripe-atlas-fe… Hosts of RIPE Atlas anchors can access the same feature via their admin interface. Other features on this "list" page of RIPE Atlas anchors are: - sortable columns: you can sort by hostname, company name, city or country; in ascending and descending order - "clickable" links to anchoring measurement per anchor, per type We hope that this will give you more insight into the operations of RIPE Atlas anchors to date. We are still accepting applications from new hosts: https://atlas.ripe.net/get-involved/become-an-anchor-host/ Regards, Vesna

3 2

does a probe "know" the AS# it is living in?
by Wilfried Woeber 19 Feb '14

19 Feb '14

Folks, a small group of people is starting to develop an idea for a new measurement and I am a memeber of that team. Now I wonder: does a probe know the AS number it is living in, or is this a piece of information that is maintained by the collectors and the various pieces of central programs and the display software? TIA, Wilfried

2 2

Re: [atlas] Logistics Q: probe "owner" leaving an organisation, but probe remains
by Alex Saroyan 19 Feb '14

19 Feb '14

Hi, Owner can transfer the probe to another host. Best Regards /Alex Saroyan Wilfried Woeber <Woeber(a)CC.UniVie.ac.at> wrote: >Hi folks, maybe there's already an FAQ answer somewhere or it has been >discussed before, and I missed it. Please point me into the right direction :-) > >Background: > >I handed out a probe (from an ambassador batch) and the probe was connected to >the 'net. Now, a rather short while later, the "owner" of that probe left the >organisation, and left the probe behind. It is still connected :-) > >What is the procedure or advice for assigning a new "owner" from the hosting >organisation? > >Thanks, >Wilfried >

2 1

Logistics Q: probe "owner" leaving an organisation, but probe remains
by Wilfried Woeber 18 Feb '14

18 Feb '14

Hi folks, maybe there's already an FAQ answer somewhere or it has been discussed before, and I missed it. Please point me into the right direction :-) Background: I handed out a probe (from an ambassador batch) and the probe was connected to the 'net. Now, a rather short while later, the "owner" of that probe left the organisation, and left the probe behind. It is still connected :-) What is the procedure or advice for assigning a new "owner" from the hosting organisation? Thanks, Wilfried

1 0

Denial of Measurement
by Sebastian Castro 18 Feb '14

18 Feb '14

Hi: Trying to investigate a problem with one of our boxes, I came across the following error message: "10 UDMs are already measuring 202.46.187.130/2001:dce:7000:2:0:0:0:130. Cannot add 1 more" What I did was to add a one-off DNS UDM to ns2.dns.net.nz, to track if reachability was OK, but I can't because someone else is already doing that. None of those UDMs is mine, so effectively someone created a "Denial of Measurement" against me. Any recommendations what to do about this? Cheers, -- Sebastian Castro Technical Research Manager .nz Registry Services (New Zealand Domain Name Registry Limited) desk: +64 4 495 2337 mobile: +64 21 400535

2 1

CERN (FR) has joined RIPE Atlas anchors
by Michela Galante 17 Feb '14

17 Feb '14

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 fr-prm-as513 and it is hosted by CERN in Prévessin-Moëns, France on behalf of RIPE NCC since they are one of our k-root hosts and RIS Remote Route Collector locations. 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, Measurements Community Building Team RIPE NCC mcb(a)ripe.net

1 0

VIX (AT) has joined RIPE Atlas anchors
by Michela Galante 13 Feb '14

13 Feb '14

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 at-vie-as1120 and it is hosted by VIX in Vienna, Austria on behalf of RIPE NCC since they are one of our RIS Remote Route Collector locations. 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, Measurements Community Building Team RIPE NCC mcb(a)ripe.net

1 0

Using RIPE Atlas for monitoring: introducing "Status Checks"
by Vesna Manojlovic 12 Feb '14

12 Feb '14

Dear colleagues, After having some of you testing Status Checks, we are now introducing this new feature to all users. It allows you to integrate RIPE Atlas into any monitoring tool you currently use, such as Nagios or Icinga. Please find a new article on RIPE Labs that explains simple steps, gives an example, and points to our future plans: https://labs.ripe.net/Members/suzanne_taylor_muzzin/introducing-ripe-atlas-… Direct link to Status Checks: https://atlas.ripe.net/docs/status-checks/ We are pleased to announce this feature that the operators community has been asking for, and we are looking forward to both your feedback and success stories. Kind regards, Vesna Manojlovic Measurements Community Building RIPE NCC

1 0

Some of the UDM results are unavailable
by Eravuchira, Steffie Jacob 12 Feb '14

12 Feb '14

Dear community, I am trying to access some of the the UDMs. I find some problems in getting results for some probes in some UDM. For example, I can access the UDM [1] and get measurements from all the probes. Whereas when I try to filter the same UDM using probe ID, the result is not available for some particular probes [2]. But it is available for some others [3] in the same UDM. [1] https://atlas.ripe.net/api/v1/measurement/1037214/result/ [2] https://atlas.ripe.net/api/v1/measurement/1037214/result/?prb_id=2330 [3] https://atlas.ripe.net/api/v1/measurement/1037214/result/?prb_id=12781 Kind Regards, Steffie

3 2

SIDN (NL) has joined RIPE Atlas anchors
by Michela Galante 06 Feb '14

06 Feb '14

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 nl-arn-as1140 and it is hosted by SIDN in Arnhem, Netherlands. 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, Measurements Community Building Team RIPE NCC mcb(a)ripe.net

1 0

Hringiðan (IS) has joined RIPE Atlas anchors
by Michela Galante 03 Feb '14

03 Feb '14

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 is-rey-as25509 and it is hosted by Hringiðan in Reykjavik, Iceland. 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, Measurements Community Building Team RIPE NCC mcb(a)ripe.net

1 0