- ripe-atlas - mailman.ripe.net

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