- ripe-atlas - mailman.ripe.net

Sharing measurement
by Lukasz Trabinski 23 Dec '14

23 Dec '14

hi It's possible to share (graphical) measurement from my ripe probe without login to my account?

4 7

Bug on credit expenditure?
by Sebastian Castro 19 Dec '14

19 Dec '14

Hi: I've created 12 one-off traceroute measurements today, each measurement requesting 38 probes. According to the results page, the number of credits per measurement is 60, at 38 probes, we got 2280 credits. Any further attempt to create new measurements returned error 104: "Executing this measurement request would violate your maximum daily spending limit of 2200000.0 credits" Unless my math is horribly wrong, or the message is incorrect, I'm well under the 2.2 million credits daily limit. Is there a bug somewhere that's miscounting the usage of credits? I have enough credits in my account to pamper myself with measurements :) 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 2

Liquid Web (Phoenix, US) has joined RIPE Atlas Anchors.
by Alastair Strachan 18 Dec '14

18 Dec '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 us-phx-as53824 and it is hosted by Liquid Web in Phoenix, United States. Congratulations to Liquid Web for their second anchor online! 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, RIPE Atlas Team

1 0

MAT-WG proposal for WLAN measurements on RIPE Atlas
by Brook Schofield 10 Dec '14

10 Dec '14

MAT-WG, thankyou for giving me the opportunity to present on "The Value of WLAN Measurements for the R&E Community" at the Measurement and Tools Working Group at RIPE69. You can find my presentation and stenography logs at: https://ripe69.ripe.net/presentations/91-eduroam-and-Atlas-RIPE69.pdf https://ripe69.ripe.net/archives/steno/40 To progress this work within the RIPE NCC Atlas development team I'd like your input into the following five (5) points: #1: For "opt-in" WLAN measurements to be enabled on RIPE Atlas As a point of clarification (and reiterated by Daniel Karrenberg) the intention is that ALL v3 probes will be capable of WLAN measurements - but measurements will ONLY be turned on by a probe host. #2: WLAN measurements will support associating to an "open" or 802.1X protected network for the purposes of performing a measurement As an active monitoring network the Atlas probes WILL NOT scan and report on all/available SSIDs. It will ONLY associate with EXPLICITLY defined SSIDs listed in the measurement. For eduroam quality purposes the success/failure of an 802.1X associations is initially the most interesting part of the measurement in determining whether sites are correctly deploying this service. There will be results related to the authentication process. #3: Any measurements performed over the wireless interface are aligned with a request to associate/authenticate to a particular network. The wireless interface will be connected only for particular tests bundled with the association to an SSID. All other tests will be performed via the wired interface as is currently the case. #4: The schedule for implementation will be determined by the RIPE NCC R&D team ...but hopefully your support for this work will allow them to prioritise this work while not jeopardising the other commitments the team has made to the community. #5: This proposal is inline with your understanding of "WiFi measurements" on the Atlas roadmap I'd be particularly interested in your feedback on whether you thought that the WiFi Measurements listed in the http://roadmap.ripe.net/ripe-atlas/ would accomplish the above or something completely different. My feeling from the room was that the above was largely accepted. I'd appreciate those that voiced their support to also do this on the mailing list again. If there's any confusion I'm willing to clarify further. Thanks, -Brook -- =================================================== Brook Schofield, Project Development Officer GÉANT Association, Singel 468 D, 1017 AW Amsterdam, The Netherlands Tel +31 20 530 4488 Fax +31 20 530 4499 Mob +31 65 155 3991 www.géant.org <http://www.xn--gant-bpa.org>

6 8

Embed links in Beta UI
by Brian Rak 10 Dec '14

10 Dec '14

The embed option in the Beta UI is *very* handy, thanks for that!

1 0

ARIN (US) has joined RIPE Atlas anchors
by Michela Galante 10 Dec '14

10 Dec '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 us-qas-as10745 and is hosted by ARIN in Ashburn, United States on behalf of the RIPE NCC. We’re very pleased that, with this latest addition, all five Regional Internet Registries are now hosting a RIPE Atlas anchor! 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, RIPE Atlas Team RIPE NCC atlas(a)ripe.net

1 0

PRT Systems Ltd (London, UK) has joined RIPE Atlas Anchors
by Alastair Strachan 10 Dec '14

10 Dec '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 uk-lon-as8676 and it is hosted by PRT Systems Ltd in London, UK. 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, RIPE Atlas Team

2 1

Núcleo de Informação e Coordenação do Ponto BR (Sao Paulo, Brazil) has joined RIPE Atlas Anchors
by Alastair Strachan 10 Dec '14

10 Dec '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 br-sao-as22548 and it is hosted by Núcleo de Informação e Coordenação do Ponto BR (Sao Paulo, Brazil) 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, RIPE Atlas Team

1 0

Dead Atlas Probe (TP-Link)
by Florian Streibelt 08 Dec '14

08 Dec '14

Hi, I got a probe returned that was not able to connect to the Atlas network. The probe was doint nothing for 2 days, only the leftmost LED (Power) was on, nothing else seems to happen. I also had to learn, that after the probe was not working, the user cleared the USB-Stick. Is there a way to resurrect the probe? Also the probe should be re-added to my ambassador account, if possible. Greetings, Florian -- Florian Streibelt, Dipl.-Inf. building MAR, 4th floor, room 4.004 Fachgebiet INET - Sekr. MAR 4-4 phone: +49 30 314 757 33 Technische Universität Berlin gpg-fp: 5BE7 F008 8B83 9357 1108 Marchstrasse 23 - 10587 Berlin 984A 3B8E A41F 82F6 1240

4 3

Credits
by Shahin Gharghi 05 Dec '14

05 Dec '14

Hi The RIPE Atlas hosts earn credit for the time their probes remain connected. I think it could be better to receive additional credit whenever someone uses that probe to make measurement. And if crowded probes be more expensive, we can distribute the load between same probes better. -- Shahin Gharghi

2 3

Liquid Web Inc. (Lansing Charter Township, US) has joined RIPE Atlas Anchors
by Alastair Strachan 04 Dec '14

04 Dec '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 us-lan-as32244 and it is hosted by Liquid Web Inc in Lansing Charter Township, United States. 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, RIPE Atlas Team

1 0

openmirrors.asia (SG) has joined RIPE Atlas anchors
by Michela Galante 03 Dec '14

03 Dec '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 sg-sin-as45494 and it is hosted by openmirrors.asia in Singapore City, Singapore, and sponsored by APNIC. 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, RIPE Atlas Team atlas(a)ripe.net

1 0

Many thanks :)
by Mike. 01 Dec '14

01 Dec '14

A short note to say 'thank-you' for the ability to configure the origination of an email message when the probe under my supervision has been offline for a short while. I was doing some work on my firewall today, and I neglected to re-plug the probe back into the USB port for power. The email informed me of my transgression. :) Mike.

3 2

Wikimedia Foundation (San Francisco, US) has joined RIPE Atlas anchors
by Michela Galante 01 Dec '14

01 Dec '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 us-sfo-as14907 and it is hosted by Wikimedia Foundation in San Francisco, United States. Congratulations to Wikimedia Foundation for their third anchor online! 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, RIPE Atlas Team

1 0

Software Probs
by Shahin Gharghi 29 Nov '14

29 Nov '14

Dear RIPE Atlas team I want to ask why don't you make software probes? RIPE NCC have to spend a lot of money on RIPE Atlas. They can easily make RIPE Atlas VMWare image or an RPM,deb package and even windows service. So people can install them on their servers. The other way to save probes is making probes multi-home. For example I have 4 probes in one place to monitor 4 different IP prefixes and paths. I know because of the hardware limits we can't use sub-interfaces but we can set 4 IP addresses manually and add 4 any route by the source, then we can save 3 other probes. -- Shahin Gharghi

5 5

MIX (IT) has joined RIPE Atlas anchors
by Michela Galante 27 Nov '14

27 Nov '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 it-mil-as16004 and it is hosted by Milan Internet eXchange (MIX) in Milan, Italy 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

Wikimedia Foundation (Carrollton, US) has joined RIPE Atlas anchors
by Michela Galante 26 Nov '14

26 Nov '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 us-cax-as14907 and it is hosted by Wikimedia Foundation in Carrollton, United States. Congratulations to Wikimedia Foundation for their second anchor online! 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, RIPE Atlas Team

1 0

Wikimedia Foundation (United States) has joined RIPE Atlas anchors
by Alastair Strachan 26 Nov '14

26 Nov '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 us-qas-as14907 and it is hosted by Wikimedia Foundation in Ashburn, United States 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, RIPE Atlas Team

2 1

Be careful with probe 4981
by Thomas Holterbach 24 Nov '14

24 Nov '14

Hi, I am going to perform some tests on our atlas probe (id 4981, ASN 3130) during the next two or three weeks. Please note that during this period, measurements from or toward this probe might be inaccurate. Thank you for your attention, Thomas

1 1

Fwd: [AFRINIC-announce] AFRINIC-RIPE Atlas Initiative
by Vesna Manojlovic 21 Nov '14

21 Nov '14

FYI -- Cooperation between AfriNIC & RIPE NCC / RIPE Atlas. Vesna -------- Original Message -------- Subject: [AFRINIC-announce] AFRINIC-RIPE Atlas Initiative Date: Fri, 21 Nov 2014 17:33:48 +0400 From: AFRINIC Communication <comm-announce(a)afrinic.net> To: announce(a)afrinic.net Dear Members/Colleagues, Following the MoU signed with the RIPE NCC in Abidjan, AFRINIC has launched an initiative to increase the number of probes and anchors in the AFRINIC service region. The “AFRINIC/RIPE Atlas Initiative” aims to support Internet measurements both globally and within our region. We are therefore relying on our members' support to help us build this network. We would also like take this opportunity to thank all those members who are already hosting probes and anchors and are keeping them online. How to Get Your AFRINIC/RIPE Atlas Probe ------------------------------------ For those who would like to support this initiative, AFRINIC and the RIPE NCC have implemented a new channel of distribution to make it easier for AFRINIC members to apply and receive their probe. If you would like to apply to host a probe, all you need to do is register online and make a request. After evaluation by the AFRINIC/RIPE NCC Atlas Team, probes will be shipped directly to successful applicants. Please note that this initiative is exclusively for AFRINIC members. More Information -------------- More information about the initiative and how to apply for and host a probe can be found athttp://www.afrinic.net/en/initiatives/afrinicripe-atlas If you are attending the AFRINIC-21 Meeting taking place from 22-28 November in Mauritius, you can also ask any AFRINIC staff member for more information about this initiative. Kind regards, AFRINIC Communications Team ................................... Chers membres/collègues, Suite au protocole d'accord signé avec le Registre Internet Regional Europeen, RIPE NCC, à Abidjan, AFRINIC a lancé une initiative visant à accroître le nombre de sondes Atlas dans la région de service d'AFRINIC. L'initiative "AFRNIC -RIPE Atlas " vise à soutenir les mesures de l'Internet au niveau mondial et au sein de notre région. Nous comptons donc sur le soutien de nos membres pour nous aider à construire ce réseau. Nous profitons de l'occasion pour remercier les membres qui hébergent déjà des sondes tout en les gardant en ligne. Comment obtenir votre sonde Atlas. Pour ceux qui sont prêts à soutenir cette initiative, AFRINIC et RIPE NCC ont mis en place une nouvelle chaîne de distribution pour les membres d'AFRINIC qui peuvent facilement faire une application et obtenir leurs sondes. Si vous souhaitez héberger une sonde, tout ce que vous devez faire est de vous inscrire en ligne et soumettre votre demande. Apres évaluation par l'Equipe d'AFRINIC-RIPE Atlas, les sondes seront directement envoyés aux candidats selectionnés par l’Equipe du projet. Plus d'informations ...................................... Plus d'informations sur l'initiative et comment faire une application pour héberger une sonde à :http://www.afrinic.net/en/initiatives/afrinicripe-atlas Si vous participez à la Réunion d'AFRINIC-21, qui se tiendra du22-28 novembre à Maurice, vous pouvez contacter le personnel d'AFRINIC pour plus d'informations sur cette initiative. L'Equipe de Communication d'AFRINIC _______________________________________________ announce mailing list announce(a)afrinic.net https://lists.afrinic.net/mailman/listinfo.cgi/announce

1 0

Using Atlas for Monitoring of Anycast DNS
by Klaus Darilion 21 Nov '14

21 Nov '14

Hi! I want to monitor an Anycasted authoritative name server: - are all nodes responding - are all nodes in routing ... So I thought about starting a long term DNS measurement with plenty of probes and NSID queried. Then, checking the results I should see every possible NSID if there are for more probes than Anycast-nodes. Does anybody have done that (or similar) already and want to share code? Can the RIPE Atlas Status Checks be used for such monitoring? Thanks Klaus

5 7

Maximum daily spending limit reached
by Ruwaifa Anwar 20 Nov '14

20 Nov '14

I'm getting this error:- "Executing this measurement request would violate your maximum daily spending limit of 1000000.0 credits". I have double checked my request. It's expected credit consumption is way less than daily limit and I don't have any other UDM running. Is there a bug in v1 API? _______________________ Regards, Muhammad Ruwaifa Anwar

3 2

Go6 Institute (SI) has joined RIPE Atlas anchors
by Michela Galante 19 Nov '14

19 Nov '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 si-lzp-as198644 and is hosted by the Go6 Institute in Skofja Loka, Slovenia, and sponsored by SIDN, Netherlands. Thank you to SIDN for sponsoring this anchor! There are more organisations that want to host a RIPE Atlas anchor but don’t have the necessary funding. To learn more about sponsoring an anchor, please contact us at mcb(a)ripe.net 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

LINX (UK) has joined RIPE Atlas anchors
by Michela Galante 18 Nov '14

18 Nov '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 uk-lon-as5459 and it is hosted by LINX in London, United Kingdom 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

Atlas Sagan library and UDP tarceroute results: bug or feature?
by Jen Linkova 18 Nov '14

18 Nov '14

Hello, I've just found that using Sagan library for analyzing UDP traceroute measurement results may produce incorrect results: 'target_responded' variable is not be set to 'True' if the source address of the traceroute reply is not the target address of the traceroute, but any other address that belongs to the node. (From the traceroute.py code: def target_responded(self): if self._target_responded is not None: return self._target_responded self._target_responded = False if self.hops and self.hops[-1].packets: destination_address = IP(self.destination_address) for packet in self.hops[-1].packets: if packet.origin and destination_address == IP(packet.origin): self._target_responded = True return self.target_responded ) I don't think that's a valid assumption that a target node is *always* choosing the probe packet's destination address as a reply source. In particular, in case of UDP packets addressed to anycast, it might fail because the node can reply from another address. In particular, rfc4443 (ICMP for IPv6) says: 2.2. Message Source Address Determination A node that originates an ICMPv6 message has to determine both the Source and Destination IPv6 Addresses in the IPv6 header before calculating the checksum. If the node has more than one unicast address, it MUST choose the Source Address of the message as follows: (a) If the message is a response to a message sent to one of the node's unicast addresses, the Source Address of the reply MUST be that same address. (b) If the message is a response to a message sent to any other address, such as - a multicast group address, - an anycast address implemented by the node, or - a unicast address that does not belong to the node the Source Address of the ICMPv6 packet MUST be a unicast address belonging to the node. == and in the same RFC source address selection for ICMP echo reply messages is defined: The source address of an Echo Reply sent in response to a unicast Echo Request message MUST be the same as the destination address of that Echo Request message. An Echo Reply SHOULD be sent in response to an Echo Request message sent to an IPv6 multicast or anycast address. In this case, the source address of the reply MUST be a unicast address belonging to the interface on which the Echo Request message was received. ==== So, I'm sending this email, first, to warn those of you who is using Sagan to analyze UDP traceroute results, and, secondly, to discuss, if Sagan behavior is a bug (I believe it is) or a feature ;) -- SY, Jen Linkova aka Furry

2 2