- ripe-atlas - mailman.ripe.net

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