- ripe-atlas - mailman.ripe.net

[dagstuhl seminar]: global measurements: practice and experience
by Bajpai, Vaibhav 12 May '16

12 May '16

Dear RIPE Atlas / MAT WG -- sorry for cross-posting. A SIGCOMM CCR article summarising the Dagstuhl seminar on ‘Global Measurements: Practice and Experience’ just came online [a]. Thought to share it with you: [a] http://www.sigcomm.org/sites/default/files/ccr/papers/2016/April/0000000-00… Background: ===================== We recently helped organise a Dagstuhl seminar on Global Measurements: Practice and Experience [b] from January 04 – 07, 2016. This was a followup of the seminar on Global Measurement Framework [c] which focused on the development of global Internet measurement platforms and associated metrics. [b] http://www.dagstuhl.de/16012 [c] http://www.dagstuhl.de/13472 The second seminar aimed at discussing the practical experience gained with building global measurement platforms. It brought together people who are actively involved in the design and maintenance of global measurement systems, who do research on the data delivered by global measurement systems, and who use data derived from global measurement systems in order to manage networks or services or as input for regulatory decisions. ===================== Best, Vaibhav =================================== Vaibhav Bajpai www.vaibhavbajpai.com Room 91, Research I School of Engineering and Sciences Jacobs University Bremen, Germany ===================================

1 0

Number of probes
by Marc Sanchez 11 May '16

11 May '16

I'm new in RIPE and I don't know it enough deeper. I need to check the state of several networks and I'm wondering how many probes should I need to measure a ping between two ASN. Could be enough using just one probe for each measurement? Sorry for the inconvenience. Sent via RIPE Forum -- https://www.ripe.net/participate/mail/forum

2 1

probe congestion?
by Paul Vlaar 11 May '16

11 May '16

Hi all, while running a DNS UDM on a fixed set of (reused from a previous UDM) probes, I noticed the following. When I start 6 UDMs against the same set using the web UI, as a one-off measurement, starting "now", the RTTs for all of the measurements shoots up on all of the probes (500-1000+ ms). When I start the 6 tests individually, the RTTs are much lower, and close to what I'd expect them to be. It appears to me that when multiple UDMs are scheduled on the same probe, these should be run in serial, not parallel, in order to not run into congestion issues. Or am I simply expecting the wrong behaviour, and should I not schedule one-off measurements in parallel in the first place? ~paul

4 6

SixXS issues
by Alison Wheeler 11 May '16

11 May '16

I received my second probe* yesterday (different ASNs) and it is connects via SixXS for IPv6 as the ISP isn't supplying native v6 (despite repeatedly asking when they will catch up on something around for twenty years!). It booted fine and the appear no issues with the IPv4 connectivity but the v6 is going up and down every few minutes (for around the same period.) Not finding anything relevant after searching the forum (nor on google) I'm trying to discover why this might be. My other machines are not experiencing any difficulty with v6 connectivity and the probe is connected to the same 16-port switch as everything else. Suggestions of what to investigate next very welcome! * https://atlas.ripe.net/probes/28800/ Sent via RIPE Forum -- https://www.ripe.net/participate/mail/forum

3 4

New on RIPE Labs: Using RIPE Atlas to Debug Network Connectivity Problems
by Mirjam Kuehne 10 May '16

10 May '16

Dear colleagues, Please find this new article by Stéphane Bortzmeyer on RIPE Labs where he explains how he used RIPE Atlas probes, the official RIP Atlas API and custom scripts, to debug network issues: https://labs.ripe.net/Members/stephane_bortzmeyer/using-ripe-atlas-to-debug… Kind regards, Mirjam Kuehne RIPE NCC

1 0

LatencyMON Widget Y axis in milliseconds
by Marat Khalili 10 May '16

10 May '16

I'm using LatencyMON <https://atlas.ripe.net/docs/tools-latencymon/> widget to monitor my network performance. It's very convenient. Unfortunately, it always loads with latency shown in %% (of what?), not in milliseconds, so I have to make one extra click in order to view actual milliseconds. Is there some hidden switch that would make milliseconds the default? Shouldn't it be initially default in the first place? -- With Best Regards, Marat Khalili

2 4

ping measurements and high lts
by Clinton Work 10 May '16

10 May '16

When looking at the ping measurement json results I found some probes are reporting a very high lts (last time synchronized). Is it normal for very high lts values to be reported? These two anchors seem chronic: Probe 6161, max lts 65807 Probe 6132, max lts 23905 ================================= Clinton Work

2 1

UDP Traceroute port?
by Laura M. Roberts 06 May '16

06 May '16

Hello, What port is used when a UDP traceroute is performed, please? Thank you, Laura

2 2

Re: [atlas] DNS entry
by Anthony 02 May '16

02 May '16

Okay thank you for the answer. Should he therefore leave the "OFF"? Le 02/05/2016 17:01, Micha Bailey a écrit : > Essentially, this is a dynamic DNS service bound to the probe. If you > choose "simple" the hostname will be something like > p#####.probes.atlas.ripe.net <http://probes.atlas.ripe.net>, with the > probe number. If you choose "obfuscated", the hostname will be > something else. I don't know exactly what it looks like, but it's > something less identifying. > > On Monday, May 2, 2016, Anthony <contact.anthoo(a)gmail.com > <mailto:contact.anthoo@gmail.com>> wrote: > > Hello, > > In the edition of general probe of my information, I see that > there are marked "DNS" with several choices: OFF, SINPLE or > obfuscated. > > I would have wanted to know what it matched? And what he had to > choose. > > Thank you in advance. >

1 0

DNS entry
by Anthony 02 May '16

02 May '16

Hello, In the edition of general probe of my information, I see that there are marked "DNS" with several choices: OFF, SINPLE or obfuscated. I would have wanted to know what it matched? And what he had to choose. Thank you in advance.

1 0

An article/FAQ entry about probe troubleshooting
by Ondřej Caletka 01 May '16

01 May '16

Hi all, it seems that failing probes are getting more and more to be an issue, possibly due to USB flash drive failure. I think it would be nice if there was an article / FAQ entry with some official troubleshooting procedures, so we could just send a link to anybody complaining about non functional probe. Is there something like this on the roadmap? Perhaps we as the community could make something up: - how to check whether the port probe is connected to has proper IP and DNS parameters and is allowed to establish a SSH session to TCP port 443 in the Internet (beware of DPI firewalls that allow HTTPS but not SSH over 443) - how to check the LED status and the SOS list at the probe page (the current LED explanation in the FAQ is too techy and even power users like me still don't understand all presented states :) ) - how to diagnose USB flash drive failure, how to force reformatting the flash drive and how to replace it with a new one What do you think? Cheers, Ondřej Caletka CESNET

9 11

Atlas probe down and probe replacement
by Vladimir-M. Obelic 30 Apr '16

30 Apr '16

After a power outage i'm not getting the probe up. It's not even trying DHCP. What is the procedure for a probe replacement? Thanks Sent via RIPE Forum -- https://www.ripe.net/participate/mail/forum

2 4

New on RIPE Labs: How Elasticsearch and Kibana Help us Analyse RIPE Atlas Data Logs
by Mirjam Kuehne 29 Apr '16

29 Apr '16

Dear colleagues, RIPE Atlas backend applications run on more than 40 servers. Each day these machines can produce thousands of application logs of any kind of severity level. In order to be able to track down serious errors, warnings or even unusual behaviour, we decided some time ago to try Elasticsearch as a logging sink. In this article we will look at the design of such a system and describe how we can easily make sense from an ocean of logs: https://labs.ripe.net/Members/andreas_strikos/how-elasticsearch-and-kibana-… Kind regards, Mirjam Kuehne RIPE NCC

1 0

Failure Rate on Atlas Probes
by Jonathan Brewer 23 Apr '16

23 Apr '16

Hi All, What's the known failure rate of Atlas probes, and the mean time before failure? At a guess 20% or more of the probes I've been working with have failed within their first year of deployment. Sometimes they come back with a power cycle, sometimes they don't. Regards, Jon

1 0

Probe not received
by rgnr＠riseup.net 22 Apr '16

22 Apr '16

Hey, as the subject says. It's been 4 weeks now and nothing has arrived. Any clues what to do? regards Bernd

2 1

Led WPS / RESET
by Anthony 22 Apr '16

22 Apr '16

Hello everyone, I had a power outage, so I had to reboot my box and my probe, but now the LED button "WPS / RESET" lights is this normal? Before it off extinct. thank you in advance

2 4

New on RIPE Labs: Looking at IXPs in Berlin with RIPE Atlas
by Vesna Manojlovic 21 Apr '16

21 Apr '16

Dear colleagues, The IXP country jedi tool described in earlier RIPE Labs articles, can now also be used to analyse the situation in a specific city. This time we look at Berlin, Germany: https://labs.ripe.net/Members/mirjam/using-ripe-atlas-to-look-at-ixps-in-be… Regards, Vesna

1 0

Probe status / self-help
by Robert Kisteleki 20 Apr '16

20 Apr '16

Dear All, Today we released a new feature intended to help the probe hosts detecting, understanding and fixing various issued related to probes. You should be able to see a new "Status" tab on your probe page. This is where we explain various conditions, such as USB problems, non-working IPv6 or DNS resolutions quirks. Please note that this bit is in early stages (officially labeled as beta). We believe it works in general, however for now it only explains various system tags that mark error conditions. It will have more features in the future. It is also intended to be a place where we can add features that explain, for example, "your probe behaves differently than the rest" or "path MTU issues detected" or such. We think this will be a useful feature to hosts. Let us know if you have specific suggestions for improvement. Regards, Robert Kisteleki RIPE NCC

3 2

*-capable ≠ *-works + *-doesnt-work
by Bajpai, Vaibhav 20 Apr '16

20 Apr '16

Hello, I am looking at the probe API data for connected probes (status = 1) for day = 20160418 system-ipv6-capable = 3556 system-ipv6-works = 2995 system-ipv6-doesnt-work = 710 Why is system-ipv6-works + system-ipv6-doesnt-work > system-ipv6-capable? system-ipv4-capable = 9336 system-ipv4-works = 9187 system-ipv4-doesnt-work = 67 Why is system-ipv4-works + system-ipv4-doesnt-work < system-ipv4-capable? Best, Vaibhav =================================== Vaibhav Bajpai www.vaibhavbajpai.com Room 91, Research I School of Engineering and Sciences Jacobs University Bremen, Germany ===================================

2 2

Question
by Anthony 19 Apr '16

19 Apr '16

Hello, I would have wanted to know if my graphs probe appears well is how well does the measures not? For you everything is ok or not? : https://atlas.ripe.net/probes/27379/ thank you in advance

2 2

RIPE Atlas CLI Toolset now available on NLNOG RING
by Vesna Manojlovic 19 Apr '16

19 Apr '16

Dear colleagues, in the spirit of cooperation between the monitoring & measuring platforms, I am happy to announce: RIPE Atlas CLI Toolset have been installed on RING! If you are already participating in NLNOG RING, now you can use RIPE Atlas CLI Toolset for "quick & dirty" access to RIPE Atlas measurements & probes. More info about RING: https://ring.nlnog.net RING nodes are also available as targets through RIPE Atlas web interface for measurements creation: https://atlas.ripe.net/targets/ringnodes/list/ https://atlas.ripe.net/targets/ringnodes/map/ Regards, Vesna Reminder about CLI tools: Source: https://github.com/RIPE-NCC/ripe-atlas-tools/ Documentation: https://ripe-atlas-tools.readthedocs.org/ In addition to "raw install", tools are also packaged in many distros: OpenBSD, FreeBSD, Gentoo, Arch, Debian and Ubuntu (in progress: Fedora, Windows). Examples of usage of RIPE Atlas CLI tools on RING: ripe@ripe01:~$ ripe-atlas report 1001 --probes 1 20 bytes from probe #1 212.238.160.244 to 193.0.14.129 (193.0.14.129): ttl=59 times:6.658, 6.591, 6.298, ripe@ripe01:~$ ripe-atlas measurements --af 6 --status ongoing --limit 15 --search nlnog Filters: Search: nlnog Af: 6 Status in: (2,) Id Type Description Status ================================================================================ 1027844 traceroute Jump Ongoing 1027846 traceroute Clara DE Ongoing 1037103 ping tenet01.ring.nlnog.net Ongoing 1404594 ping RedpillLinpro-v6 Ongoing 1596748 ping world4you01.ring.nlnog.net Ongoing 1688325 ping ping6 on amazon03 Ongoing 3678270 traceroute Traceroute measurement to bluezonejordan01 Ongoing ================================================================================ Showing 7 of 7 total measurements ripe@ripe01:~$ ripe-atlas configure --setauthorisation.create=7b4c-xxxx ripe@ripe01:~$ ripe-atlas measure ping --target ping.xs4all.nl Looking good! Your measurement was created and details about it can be found here: https://atlas.ripe.net/measurements/3671547/ Connecting to stream... 48 bytes from probe #6174 217.10.140.74 to 194.109.6.8 (194.109.6.8): ttl=56 times:8.849, 8.781, 8.78, 48 bytes from probe #26941 88.85.47.152 to 194.109.6.8 (194.109.6.8): ttl=55 times:74.372, 74.487, 74.748, 48 bytes from probe #24596 176.144.180.224 to 194.109.6.8 (194.109.6.8): ttl=57 times:45.418, 45.249, 45.5, 48 bytes from probe #6187 196.10.54.135 to 194.109.6.8 (194.109.6.8): ttl=56 times:155.65, 155.58, 155.668, 48 bytes from probe #3207 37.49.102.93 to 194.109.6.8 (194.109.6.8): ttl=50 times:24.4, 27.627, 21.95, 48 bytes from probe #6186 82.195.72.11 to 194.109.6.8 (194.109.6.8): ttl=58 times:7.087, 7.101, 7.052, ... Read more about it on RIPE Labs: https://labs.ripe.net/Members/suzanne_taylor_muzzin/announcing-the-cli-tool…

1 0

API filtering for looking at measurements?
by Baptiste Jonglez 18 Apr '16

18 Apr '16

Hi, I would like to find measurements matching some specific conditions, so I tried to use the measurement API documented here: https://atlas.ripe.net/docs/rest/ However, filters don't seem to have the intended effect. For instance, I tried to restrict to a specific range of starting time: https://atlas.ripe.net/api/v1/measurement/?start_time__gte=1443654000&start… but looking at the first result (measurement ID 1411440), its start time is 1564618500, which is way outside of the requested range. Similarly when filtering by type: https://atlas.ripe.net/api/v1/measurement/?type=2 type=2 is supposed to be IPv4 traceroute, but the first result is measurement ID 1001, which is an IPv4 ping. Am I using the API incorrectly, or is there a bug somewhere? Thanks, Baptiste

2 2

Open ports?
by Anthony 15 Apr '16

15 Apr '16

Hello, I received my probe today and I had to disable the firewall for my box that appears connected to the site. I reactivated and after all the work area, but I would have liked to know what need had to open? How to know if everything is ok? Sorry for my English, thank you in advance

4 5

Incorrect probe connection information?
by Max Mühlbronner 13 Apr '16

13 Apr '16

Hi, I think there is a small bug/issue with the statistics of the probe (Tab : "Network") : Connection Information Time Connected Percent Last Week 9d 10h 2m 100.00% Last Month 55d 10h 2m 100.00% How could it be that Last Month my probe was connected for 55 days? (It's only a single probe) Any idea? Best Regards Max M.

3 3

Introducing the RIPE Forum
by Vesna Manojlovic 12 Apr '16

12 Apr '16

Dear colleagues, There’s a new way to participate on the RIPE Atlas mailing list! We are introducing the RIPE Forum, a web-based interface for reading and sending emails on RIPE community mailing lists. We developed the RIPE Forum in-house based on feedback we received from members of the RIPE community who wanted the option to interact and share information in a more modern way. But it’s important to note that this new interface is completely optional – those who like using the established mailing list system can continue on as they always have, and won’t notice any difference. RIPE Atlas mailing list will be the first one. We have plans to make the RIPE Forum available for other RIPE Community mailings lists after the RIPE 72 Meeting in May. If you’re interested, you can start using it here: https://www.ripe.net/participate/mail/forum/ We created a special mailing list for testing purposes, so that any conversations about the platform itself can be contained there without disrupting the regular flow of discussions on the RIPE Atlas mailing list. Feel free to send test messages and try out the RIPE Forum on this special list: https://www.ripe.net/participate/mail/forum/ripe-forum-test Learn more how the forum works and the background of the project: https://labs.ripe.net/Members/marco_schmidt/introducing-the-ripe-forum The forum is still in "beta" status – there are likely still some bugs and we are continuously working to improve things, so please keep that in mind while exploring the forum. You can give your feedback by clicking on the “Report a bug” button on the forum, or leave a comment on the above RIPE Labs article. We hope you’ll enjoy the RIPE Forum, and look forward to your feedback! Kind regards, Vesna Sent via RIPE Forum -- https://www.ripe.net/participate/mail/forum

3 2