- ripe-atlas - mailman.ripe.net

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

Ooredoo (QA) 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 qa-doh-as8781 and it is hosted by Ooredoo in Doha, Qatar on behalf of RIPE NCC since they are one of our K-root hosts. This is the first anchor in Middle East. 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

Lanka Education & Research (LK) has joined RIPE Atlas anchors
by Michela Galante 17 Nov '14

17 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 lk-cmb-as38229 and it is hosted by Lanka Education & Research in Colombo, Sri Lanka. This is the first of ten anchors that APNIC will sponsor. 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

Booking.com (NL and UK) has joined RIPE Atlas anchors
by Michela Galante 17 Nov '14

17 Nov '14

Dear RIPE Atlas users, We're happy to announce that two RIPE Atlas anchors have joined the network and are now available as targets for probe hosts conducting their own user-defined measurements. The new anchors are nl-ams-as43996 located in Amsterdam, Netherlands and uk-slo-as43996 located in Slough, United Kingdom, both hosted by Booking.com. Congratulations to Booking.com for bringing their two anchors 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, Measurements Community Building Team RIPE NCC mcb(a)ripe.net

1 0

KazNIC Organization (KZ) has joined RIPE Atlas anchors
by Lia Hestina 14 Nov '14

14 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 kz-plx-as21282 and it is hosted by KazNIC Organization in Semey, Kazakhstan. 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

skHosting.eu (SK) has joined RIPE Atlas anchors
by Michela Galante 12 Nov '14

12 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 sk-bts-as201702 and it is hosted by skHosting.eu in Bratislava, Slovakia. 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 configurasble 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

Built-in IPv6 measurements not working
by Matteo Bonora 07 Nov '14

07 Nov '14

Hello, I have noticed that my probe (#14602) doesn't perform the IPv6 built-in measurements since about 5 months. The probe has working IPv6 connectivity, so I can't understand where is the problem. Anyone has an idea about what can I do to solve this? (below you can see some graphs of my probe's measurements. The brief packet loss on IPv4 was due to a temporary network outage) Thanks for your help! Matteo

4 7

Re: [atlas] [mat-wg] New on RIPE Labs: New RIPE Atlas Measurements User Interface
by Steffie Jacob Eravuchira 04 Nov '14

04 Nov '14

Hello, On 10/28/2014 04:25 PM, Mirjam Kuehne wrote: > Dear colleagues, > > We're very excited to announce an all-new user interface for RIPE Atlas > measurements. Users can now schedule, monitor and manage their own > customised measurements more efficiently than ever before, and can now > make use of the tagging feature when selecting probes for use in those > measurements. Learn more about the new features on RIPE Labs and let us > know what you think: > > https://labs.ripe.net/Members/suzanne_taylor_muzzin/ripe-atlas-new-measurem… The new user interface for RIPE Atlas measurements looks well-designed. In the old interface, the "Target" field allows us to choose from a drop-down list of anchors/ringnodes. But in the new interface, the "Target" field is just a text field. Given, as a user, I do not know the hostnames of all anchors, would it be possible to bring the drop-down anchor list feature back? Thanks. -- Regards, Steffie _______________________________________________ Steffie Jacob Eravuchira Research I, Room 91 Computer Networks and Distributed Systems (CNDS) Lab School of Engineering and Sciences Jacobs University Bremen, Germany

6 5

Measurement UI beta
by Mike. 03 Nov '14

03 Nov '14

I just had a chance to look at the beta for the MeasurementUI. Is there a specfic reason why RIPE is using the very low-contrast light grey letters on a white background? Why make it more difficult to read?

1 0