October 2014 - ripe-atlas - mailman.ripe.net

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

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

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

Data Streaming in RIPE Atlas
by Vesna Manojlovic 31 Oct '14

31 Oct '14

Dear colleagues, RIPE Atlas data is now available as a live data stream, opening the door to a host of new applications and use cases. You can read more about this new functionality (and watch the video!) on RIPE Labs: https://labs.ripe.net/Members/suzanne_taylor_muzzin/data-streaming-in-ripe-… Please let us know if you make a cool use of this new feature! Kind regards, Vesna

1 0

MTR measurement support
by Aris Tzermias 31 Oct '14

31 Oct '14

Dear all, I was wondering whether you plan to provide an MTR ( https://en.wikipedia.org/wiki/MTR_%28software%29) support as a User-defined measurement. Best regards,

2 1

SSL error when connecting to https://atlas.ripe.net/
by Gilles Pion 29 Oct '14

29 Oct '14

I'm suddenly unable to connect to https://atlas.ripe.net/ When using Firefox I'm getting the error "ssl_error_no_cypher_overlap" Whith Google Chrome: "ERR_CONNECTION_CLOSED" I'm only able to connect With IE, providing SSLV2 is enabled in advanced options (not a good idea I presume) NB: I'm behind a corporate proxy. -- *Gilles*

5 5

Re: [atlas] Fwd: Your RIPE Atlas Probe (ID: 11513) is now connected to our network
by Rusty Dekema 26 Oct '14

26 Oct '14

Greetings, I do not know anything about probes 14203 or 16058. The only probes I am involved with / responsible for are 10555 and 11513. Cheers, Rusty D On Mon, Oct 20, 2014 at 1:16 AM, Phillip Remaker <remaker(a)gmail.com> wrote: > Thanks for the update! > > Can you give me any insight into #14203 and #16058? > > 16058 is particularly troubling, since it never seems to have come up in > the first place. I have it connected and powered up, with no joy. Is > there any way to fully reset it? > > On Sun, Oct 19, 2014 at 6:49 PM, Rusty Dekema <rdekema(a)gmail.com> wrote: > >> Good evening, >> >> In case you track these sorts of things, the ~2 week disconnection of >> this probe was caused by network trouble on my end (combined with an >> extended vacation), and not by the probe itself or any other part of the >> RIPE Atlas system. >> >> Cheers, >> Rusty Dekema >> >> ---------- Forwarded message ---------- >> From: RIPE Atlas <atlas(a)ripe.net> >> Date: Sun, Oct 19, 2014 at 9:40 PM >> Subject: Your RIPE Atlas Probe (ID: 11513) is now connected to our network >> To: rdekema(a)gmail.com >> >> >> Dear RIPE Atlas probe host, >> >> Thank you for participating in RIPE Atlas! >> >> We're just letting you know that your probe (#11513 with description >> Comcast Business 50/10 (with IPv6 trial).) has re-established its link to >> our network and we are again receiving data from it. For your own records, >> it appears that the reconnection took place at 2014-10-20 01:39 UTC. >> >> If you have any questions, please contact us at atlas(a)ripe.net >> >> Best regards, >> >> RIPE Atlas Team >> >> ********** >> You are receiving this message because you applied for or were given a >> RIPE Atlas probe. We will only send messages when your probe becomes >> disconnected for an extended period of time. >> >> >

1 0

Fwd: [mat-wg] RIPE Atlas Value Proposition Published
by Vesna Manojlovic 24 Oct '14

24 Oct '14

Dear colleagues, please take a look at this news about RIPE Atlas, at mat-wg list. Regards, Vesna -------- Original Message -------- Subject: [mat-wg] RIPE Atlas Value Proposition Published Date: Fri, 24 Oct 2014 15:02:14 +0200 From: Kaveh Ranjbar <kranjbar(a)ripe.net> To: mat-wg(a)ripe.net Dear colleagues, During its meeting in September, the RIPE NCC presented the RIPE NCC Executive Board with a value proposition document detailing the value that RIPE Atlas can bring to network operators, researchers and the Internet community as a whole. The board asked the RIPE NCC to publish this document, which is available on RIPE Labs: https://labs.ripe.net/Members/suzanne_taylor_muzzin/ripe-atlas-value-propos… We also plan to incorporate much of the document's content into the RIPE Atlas website so that RIPE Atlas users can clearly understand the different ways this global Internet measurement network can be used and the many unique benefits it provides. We hope you will find this document useful and that you may even be inspired to make use of RIPE Atlas in new ways. Kind regards, Kaveh Ranjbar Chief Information Officer RIPE NCC

1 0

RIPE 69: Learn More About RIPE Atlas and RIPEstat!
by Vesna Manojlovic 24 Oct '14

24 Oct '14

Dear colleagues, Attending RIPE 69 in London? If so, you can learn more about RIPE Atlas and RIPEstat at our sessions: Tutorial: "Basic RIPE NCC Tools for Network Diagnostics and Monitoring" When: Monday, 3 November 2014, 09:00-11:00 Where: Bourg meeting room, mezzanine floor More information about the RIPE 69 tutorials is available online: https://ripe69.ripe.net/programme/meeting-plan/tutorials/ Workshop: "Advanced Topics in RIPE Atlas Usage" When: Tuesday, 4 November, 18:00–19:00 (date might change!) Where: Side Room More information: https://ripe69.ripe.net/programme/meeting-plan/workshops/ This is an opportunity to exchange experiences, ask questions, and learn from each other. I hope to see you in London! Regards, Vesna

1 0

2Day Telecom LLP (KZ) has joined RIPE Atlas anchors
by Michela Galante 23 Oct '14

23 Oct '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-ala-as21299 and it is hosted by 2Day Telecom LLP in Almaty, Kazakhstan. With this anchor we reached a total of 80 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

RIPE atlas probe network configuration
by James A. T. Rice 21 Oct '14

21 Oct '14

Hi RIPE, We've just obtained our final /22 of IPv4 PA space, and we're looking at doing things a little differently with regards to trying to maximise the efficiency of usage within that block. While 100% utilisation of IP addresses by customers is not difficult in e.g. broadband networks (with a /32 being routed over a point to point link to each user), it is difficult in ethernet networks (with 2^n size subnets, network and broadcast and router addresses). Essentially we're going to try to have each customer device (for this purpose, the RIPE atlas probe is a customer device) consume exactly the number of globally unique IP addresses that it needs. Because for isolation each customer gets their own VLAN, and because "ethernet" traditionally means subnets with 2^n size and network and broadcast addresses and physical router addresses and VRRP addresses needing to be on that subnet, we end up with a subnet of 8 IP addresses used for a customer device that only will have 1 IP address exposed to the outside world: globally unique range: 0 - network 1 - default gateway vrrp 2 - router-a physical 3 - router-b physical 4 - customer device .. .. 7 - broadcast What I'd like to do, in order to only consume 1 globally unique IP address for the whole setup is as follows: private range, e.g. 10.a.b.c/24 0 - network 1 - default gateway vrrp 2 - router-a physical 3 - router-b physical 4 - customer device .. .. 255 - broadcast with a single globally unique IPv4 /32 (let's say) p.q.r.s routed to 10.a.b.4 in the above example. This means that you'd need to configure on your device, something like (assuming linux): network: 10.a.b.0/24 gateway: 10.a.b.1 alias: p.q.r.s/32 with it configured that p.q.r.s is the default source IP address to use for any outbound packets. This is a relatively 'clean' way of doing things, as it doesn't involve proxy-arp or similar trickery. It should be possible to do this for linux based systems. What do you think? Will the atlas probe support it, or would you consider making that a feature? Thanks James Rice Jump Networks Ltd.

2 3

Afilias (NL) has joined RIPE Atlas anchors
by Michela Galante 20 Oct '14

20 Oct '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-ams-as12041 and it is hosted by Afilias in Amsterdam, 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

Fwd: Your RIPE Atlas Probe (ID: 11513) is now connected to our network
by Rusty Dekema 20 Oct '14

20 Oct '14

Good evening, In case you track these sorts of things, the ~2 week disconnection of this probe was caused by network trouble on my end (combined with an extended vacation), and not by the probe itself or any other part of the RIPE Atlas system. Cheers, Rusty Dekema ---------- Forwarded message ---------- From: RIPE Atlas <atlas(a)ripe.net> Date: Sun, Oct 19, 2014 at 9:40 PM Subject: Your RIPE Atlas Probe (ID: 11513) is now connected to our network To: rdekema(a)gmail.com Dear RIPE Atlas probe host, Thank you for participating in RIPE Atlas! We're just letting you know that your probe (#11513 with description Comcast Business 50/10 (with IPv6 trial).) has re-established its link to our network and we are again receiving data from it. For your own records, it appears that the reconnection took place at 2014-10-20 01:39 UTC. If you have any questions, please contact us at atlas(a)ripe.net Best regards, RIPE Atlas Team ********** You are receiving this message because you applied for or were given a RIPE Atlas probe. We will only send messages when your probe becomes disconnected for an extended period of time.

1 0

Http Measurements
by Robert Vojcik 10 Oct '14

10 Oct '14

Hi, I'm preparing some measurements for our project because we plan to migrate one big site from CDN. I saw in documentation that Atlas support HTTP measurements but not for all users by default. How can I request this feature ? We will have ping and traceroute measurements but HTTP reponses would be great to compare what impact migration will have. Thank you for help -- Robert

2 1

teamix (DE) has joined RIPE Atlas anchors
by Michela Galante 08 Oct '14

08 Oct '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 de-nue-as33988 and it is hosted by teamix GmbH in Nuremberg, Germany. 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

Comcast (US) has joined RIPE Atlas anchors
by Michela Galante 07 Oct '14

07 Oct '14

Dear RIPE Atlas users, We're happy to announce that another RIPE Atlas anchor 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-den-as7922 and it is hosted by Comcast in Denver, United States. Congratulations to Comcast 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, Measurements Community Building Team RIPE NCC mcb(a)ripe.net

1 0

RIPE Atlas vs. bash/shellshock vulnerability
by Robert Kisteleki 03 Oct '14

03 Oct '14

Dear RIPE Atlas users, The RIPE NCC made a public announcement earlier about this issue (see https://www.ripe.net/internet-coordination/news/announcements/ripe-ncc-secu…) Still, since we have received some questions in email and Twitter about RIPE Atlas vs. this vulnerability so we'd like to respond to these with some more detail. The RIPE Atlas v1-v2-v3 probes are/were not affected by this issue at all since they don't run bash (or even have it installed) and also not providing any accessible services. The anchors have bash installed, but it is not used for any of the services provided. Besides, these servers have been patched right away. The infrastructure components (ie. controllers) were affected and as the RIPE NCC announcement explains, they have been patched as soon as the patch came out; basically within the day. Regards, Robert Kisteleki for the Atlas team

3 3

out of office
by jiri.prochazka＠superhosting.cz 01 Oct '14

01 Oct '14

Dear sender, I am currently out of office returning October 6th. I have limited access to my email, in urgent case you can reach me on my mobile phone + 420 777 87 37 67. Regards, -- Jiri Prochazka network administrator (AS39392) SuperNetwork s.r.o. m: +420 777 87 37 67 w: http://www.superhosting.cz e: jiri.prochazka(a)superhosting.cz

1 0

Wrong uptime information in monthly report
by Rene Bartsch 01 Oct '14

01 Oct '14

Hi, I got the following report of a drone: -------------------------------------------------------------------------------------------------------------- This is your monthly availability report for probe 3146 (T-Online Call & Surf Comfort IP Speed 50/10 MBit/s ). Calculation interval : 2014-09-01 00:00:00 - 2014-10-01 00:00:00 Total Connected Time : 15d 16:46 Total Disconnected Time : 14d 07:13 Total Availability : 52.33% +---------------------+---------------------+------------+--------------+ | Connected (UTC) | Disconnected (UTC) | Connected | Disconnected | |---------------------+---------------------+------------+--------------+ | 2014-08-14 11:37:26 | 2014-09-02 02:22:27 | 1d 02:22 | 0d 00:00 | | 2014-09-02 02:36:21 | 2014-09-04 23:40:28 | 2d 21:04 | 0d 00:13 | | 2014-09-05 00:03:58 | 2014-09-16 17:23:55 | 11d 17:19 | 0d 00:23 | +---------------------+---------------------+------------+--------------+ ---------------------------------------------------------------------------------------------------------------- https://atlas.ripe.net/probes/3146/#!tab-network shows an uptime of 99.83%. Please fix this! -- Best regards, Renne

2 1