- ripe-atlas - mailman.ripe.net

ripe.atlas.net issues
by Max Mühlbronner 06 Oct '16

06 Oct '16

"Oops - this page experienced an error while loading." My atlas / My probe does not work, the checks are failing. (Since ~12 minutes) Please don't tell me that it's maintenance work again, without any announcement? ;) Max M.

5 7

SSL error on OpenIPMap
by Anurag Bhatia 04 Oct '16

04 Oct '16

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Hello everyone. Is it just me or anyone else getting SSL error on OpenIPMap? I can see that SSL cert of atlas.ripe.net is valid but when we open OpenIP Map, it calls one specific map image from fastly on HTTP resulting in "mixed content" making Chrome to throw SSL error. This is the URL of that image:http://stamen-tiles-c.a.ssl.fastly.net/toner-lite/3/5/5.png It does seems to be available on https already and so probably someone at RIPE need to update URL to call https in URL and avoid the false positive it's giving. Thanks. - -- Anurag Bhatiaanuragbhatia.com -----BEGIN PGP SIGNATURE----- Version: Mailvelope v1.5.2 Comment: https://www.mailvelope.com wsFcBAEBCAAQBQJX7qbdCRDAbdUkJF5Y4gAAP7oP/R+c7QMQEIt7c0/fLnKx IrvoSxS0RlivGHQBcQY4DcQvXNU0SsBdjUTG3hOJP/OyCERG9Uar8xRFXKAB LHrUGPa9rGdxHtJFJYL0fgKc0o0aELBkaot3unJPBRwGtp5Acyfx3Yv9CUF+ fqxq27tRnRtXklqVfYw5aWC20CC4EHEme3vv0+QsdasJ0s1mi1zehI1c60yI RQqZ35MaB9flyMyxU1L2CaKHh0BnZs0ssSxGsr/s2cfqhfu5KPzagi/obsEs 6mhwtkTPD1Y/649QAzs2E3vpZ83tn8fkExU54hHznpBy4QmNIAx7pnlwtOrX 8ou7Rn1Yt7V5NiSHGkr31sPJfMfHXErZ6NAl/Z7uPcs9+ofAkAEBh5H7pINr BFwZzX6DsqNiq1Q+F9sU385D5144Y4YE/vDIDXYXhSgbHv9NeqIph7Ceitt9 Ap4wx7eOh/8ONLddUdqf4/M0m9ORsFc4fRAhFkLCzLdUlXpDqAGGgxSFIcg4 NiInbdyZCO1Ula7TQCPR0qtTDJQ75w93wj5STM2uZjlVd5K6QUB4bmz8S/QX oEMLOSmjcWybQH+dBSJ25VVynCu7sRkSUyhyE2wwrb2adDw8pS0QMG5cyjhZ DX+XP9KGoFi6xYFCQypXO+bkSsh84OBKrxo+fFfznFTYFkDZ6yae/ZKSfC/o urP4 =coGp -----END PGP SIGNATURE-----

2 2

Inconsistent system tags
by Johannes Matheis 30 Sep '16

30 Sep '16

Hello, I got IPv6 connectivity for my probe 4365 a few days ago (2016-09-26) when I first noticed the system tag "IPv6 Doesn't Work". As the system tags aren't updated more often than every four hours I started some successful IPv6 measurements on that probe and settled back for four days. Now the probe is still flagged as IPv6 not working. In the meantime I noticed the tag "v2" but the general information tab tells me the system architecture is probev1… Actually I don't know if it's a v1 or v2, but it's still an old Lantronix one, so it's not completely wrong :-) Is there a possibility to re-trigger the assignment of the system tags for this probe or some other solution? Thanks! jomat

2 1

Initiating a TCP, UDP, and ICMP traceroutes from the same probe at the same time
by Zakaria Al-Qudah 30 Sep '16

30 Sep '16

Hi Folks, I am planning an experiment where I need each probe to perform TCP, UDP, and ICMP traceroutes at the same time. I could not see how I can do it using the Ripe Atlas website. Is there any way to do it? Best regards, Sent via RIPE Forum -- https://www.ripe.net/participate/mail/forum

3 2

Making public probes’ IP addresses public in web interface
by Andreas Strikos 30 Sep '16

30 Sep '16

Hello, We made a change a few weeks ago to the RIPE Atlas web interface to align it more closely with the API. As a result, you can now see the IP addresses for public probes, regardless of whether you are a logged in user or not. This information is displayed on the public probes’ detailed information pages, under the “Network” tab. Previously, public probes' IP addresses were not shown, even for logged in users. Nothing has changed in the API or the web interface for probes that are not shared publicly. We understand that some of you were surprised by this change and we apologise for not communicating it earlier. However, I want to make it clear that the IP addresses of public probes have always been available via the API, whether you are a logged in user or not. We decided to include it via the web interface so that our users could access the same information regardless of which interface they decide to use. RIPE Atlas is meant to be a public platform that openly provides data to everyone interested. In this spirit, we encourage everyone to make their probes public. However, if you decide that you *don’t* want to share your probe publicly, you can change this setting by going to your probe’s detailed information page (go to "My Atlas" and click on your probe’s ID), clicking on the “Edit” button under the “General Information” tab, and deselecting the “Shared Publicly” box. Please note that personal information such as MAC addresses and email addresses will never be shown, regardless of whether you decide to share your probe publicly or not. You can learn more about what information is made public in RIPE Atlas in this RIPE Labs article: https://labs.ripe.net/Members/becha/proposing-making-ripe-atlas-data-more-p… Please let us know if you have any questions or concerns. Regards, Andreas Strikos RIPE NCC

1 0

Fifteen new RIPE Atlas anchors - including the first IPv4-only anchor
by Michela Galante 19 Sep '16

19 Sep '16

Dear colleagues, Fifteen new RIPE Atlas anchors have been activated since our last announcement in June, bringing the total number to 216: - us-abn-as54054, hosted by Deteque LLC in Ashburn, United States - us-sgu-as46309, hosted by Gartner Inc in Saint George, United States - lu-kay-as35733, hosted by EURid VZW in Kayl, Luxembourg - de-ham-as35258, hosted by akquinet Outsourcing in Hamburg, Germany - ua-iev-as24725, hosted by Hostmaster LLC in Kiev, Ukraine - ca-wnp-as18451, hosted by les.net in Winnipeg, Canada - de-dus-as12676, hosted by HKN GmbH in Düsseldorf, Germany - uk-lon-as34587, hosted by bet365 in London, United Kingdom - us-lax-as15133, hosted by Verizon Digital Media in Los Angeles, United States - us-lwc-as2495, hosted by KanREN Inc in Lawrence, United States - lb-bey-as12812, hosted by the American University of Beirut in Beirut, Lebanon (IPv4-only anchor) - pg-pom-as17828, hosted by Telikom PNG (sponsored by APNIC) in Port Moresby, Papua New Guinea - ch-zrh-as9092, hosted by Open Systems in Zurich, Switzerland - nl-ams-as34106, hosted by TMG/Telegraaf in Amsterdam, Netherlands - dk-hje-as39642, hosted by WNB ApS in Højer, Denmark You can find the full list of anchors, a map of their locations, a list of the hosting organisations and more information about RIPE Atlas anchors online: https://atlas.ripe.net/anchors/list/ As a follow-up to some discussion on this list, we wanted to reiterate that we made the decision to support IPv4-only anchors because the goal of RIPE Atlas is to measure as much of the Internet as possible, and right now, that includes IPv4-only networks. We also believe that measuring networks before and after they enable IPv6 provides useful data. IPv4-only anchors are clearly marked as such, and we will implement checks to ensure these anchors become IPv6-capable as soon as their ASNs begin announcing IPv6. In the meantime, the RIPE NCC will continue to actively promote IPv6 deployment through our training courses, IPv6 Act Now website, IPv6 Roadshows and other programs, and our IPv6 Program Manager will follow up with any hosts requesting an IPv4-only anchor to help them in any way possible. We believe that supporting IPv4-only anchors will provide a more comprehensive understanding of the Internet and that the entire Internet community will benefit from more measurement data. You can learn more in this RIPE Labs article: https://labs.ripe.net/Members/suzanne_taylor_muzzin/ipv4-only-ripe-atlas-an… Interested in hosting a RIPE Atlas anchor? Learn more: https://atlas.ripe.net/get-involved/become-an-anchor-host/ We are particularly interested in deploying anchors in the Middle East, Western Asia, Latin America and Africa in order to add more geographical diversity to the measurement data. There are several organisations that want to host a RIPE Atlas anchor but don’t have the necessary funding. To learn more about sponsoring an anchor, or for any other questions, please contact us at atlas(a)ripe.net And don’t forget to let us know if you’re doing something interesting with RIPE Atlas data - we always want to hear about your use cases, research and experiences! Regards, Michela Galante RIPE NCC

1 0

"Invalid target" error for RFC 1918 space
by Yang Yu 18 Sep '16

18 Sep '16

Hi, I got "Invalid target" error when I tried to create a measurement to see how far some RFC 1918 prefixes got propagated (carrier not properly filtering customer announcement). What is considered invalid for each measurement type? Thanks. Yang

4 4

New on RIPE Labs: Using RIPE Atlas to Monitor Game Service Connectivity
by Mirjam Kuehne 14 Sep '16

14 Sep '16

Dear colleagues, Annika Wickert, a network engineer at a gaming company, describes how she used RIPE Atlas to monitor her company's services and improve their customers' experience - and even decided to become a RIPE Atlas sponsor! https://labs.ripe.net/Members/annika_wickert/using-ripe-atlas-to-monitor-ga… Kind regards, Mirjam Kuehne RIPE NCC

1 0

meaning of error message in Ping measurements
by Wenqin SHAO 13 Sep '16

13 Sep '16

Dear list, Could someone please help me figure out what these error messages in result field of ping measurement mean? - error: sendto failed: Invalid argument (related to name resolve?) - error: sendto failed: Bad file descriptor Many thanks. Best regards, wenqin

2 2

Re: [atlas] Rate limits on Atlas
by Emile Aben 09 Sep '16

09 Sep '16

On 08/09/16 14:01, Anant Shah wrote: > Hi Emile, > > Roya and I are working on a geolocation paper and want to use the atlas > probes to ping target IPs. > > I think I am hitting the rate limit on atlas even with 99 concurrent > measurements. All my measurements now show Forbidden status. Is there a > way to increase the limit? yes, ask the team at atlas(a)ripe.net (cc-ed). the folks there can extend limits (not unlimited of course, these limits are there for a reason :) ), but would need some info from you: - what is the experiment you'd like to perform - what would you want the new limit to be (and why what you want to do can't be done with the current limits and/or existing measurements) - when does your experiment end (ie. when can we put the limits back to the default) - promise us that you'll acknowledge RIPE Atlas in a paper - send us a link/copy of the paper once it's published (i hope i'm not forgetting things :) ) cheers, emile

1 0

API probe search
by Hank Nussbacher 08 Sep '16

08 Sep '16

When searching for specific ASN probes via: https://atlas.ripe.net/probes/ and entering a search like "ASxxxx", why does the API ignore the letters AS and respond with probes that have an id of yxxxx or xxxxy or ASN yxxxy? Shouldn't it be if I specify a specific string of ASxxx the response should be *only *those probes in ASxxx or at the worst also ASxxxy? Thanks, Hank

3 5

Data delays on RIPE Atlas
by Romeo Zwart 08 Sep '16

08 Sep '16

Dear colleagues, We are performing some maintenance work on the backend clusters supporting RIPE Atlas. Unexpectedly, this is having an impact on the insertion speed of new data. This means that new data insertion is behind for a few hours. The maintenance work is expected to complete before the end of the day, at which point the backlog of data will be cleared up very quickly. We apologise for any inconvenience caused. Kind regards, Romeo

1 0

New on RIPE Labs: Using RIPE Atlas to Measure Cloud Connectivity
by Mirjam Kuehne 06 Sep '16

06 Sep '16

Dear colleagues, Please find this new article on RIPE Labs describing how to compare connectivity of cloud services using RIPE Atlas measurements. This article has been contributed by Jason Read: https://labs.ripe.net/Members/jason_read/using-ripe-atlas-to-measure-cloud-… Kind regards, Mirjam Kuehne RIPE NCC

2 1

Changes in LatencyMon
by Marat Khalili 05 Sep '16

05 Sep '16

Dear list, LatencyMon <https://atlas.ripe.net/docs/tools-latencymon/> changed for me recently with only minimum latency value shown now instead of all three. I wonder if other people see this and what are the reasons behind the change? (Cannot say yet if changes are for better or worse, but I can find no announcement and so suspect that this can be unintentional.) -- With Best Regards, Marat Khalili

2 1

New on RIPE Labs: Another Look at RIPE Atlas Probe Lifetimes
by Mirjam Kuehne 26 Aug '16

26 Aug '16

Dear colleagues, We took another, more detailed look at probe lifetimes and the dynamics of probes connecting and disconnecting from the RIPE Atlas infrastructure to try to understand how to keep the network growing in the long term. https://labs.ripe.net/Members/wilhelm/another-look-at-ripe-atlas-probe-life… Kind regards, Mirjam Kuehne RIPE NCC

7 6

Reconnecting probe 3508 - troubleshooting
by Michael-John Turner 24 Aug '16

24 Aug '16

Hi I've just reconnected probe 3508 to the network after a number of years offline (I think it was last online in November 2012?). Under the SOS history, I can see that it's making DNS queries successfully (using the DNS servers it receives by DHCP), but it's not connecting correctly to the RIPE network. The following is also displayed under SOS history: "This probe cannot connect on port 443 (HTTPS)". Any thoughts on where I can start troubleshooting? For test purposes I've connected the probe to my LAN, with full internet access. Cheers, MJ -- Michael-John Turner * mj(a)mjturner.net * http://mjturner.net/

7 10

Atlas Sagan error_message
by Wenqin SHAO 24 Aug '16

24 Aug '16

Dear list, I was using ripe.atlas.sagan to parse some ping measurements, one of them looks like the following in JSON format: rec = {u'af': 4, u'prb_id': 15843, u'result': [{u'error': u'connect failed: Network is unreachable'}], u'avg': -1, u'size': 20, u'from': u'88.174.18.20', u'proto': u'ICMP', u'timestamp': 1470009620, u'dup': 0, u'type': u'ping', u'sent': 0, u'msm_id': 1010, u'fw': 4730, u'max': -1, u'step': 240, u'src_addr': u'192.168.0.22', u'rcvd': 0, u'msm_name': u'Ping', u'lts': 641089, u'dst_name': u'192.228.79.201', u'min': -1, u'dst_addr': u'192.228.79.201'} Suppose that the above measurement is stored in a variable called rec as a dict, and I parse it using PingResult: from ripe.atlas.sagan import PingResult parsed_rec = PingResult(rec) I was expecting a no-empty string for parsed_rec.error_message, as we can see the measurement result contains an error string, however the parsed_rec.error_message is None. type(parsed_rec.error_message) <type 'NoneType’> Probably I misunderstood some part of the doc: error_message str If the result is an error, the message string is in here Could someone please clarify the exact functionality of this error_message? Many thanks in advance. Best, wenqin

1 0

Probe 10973 problem
by Vladislav Solovei 17 Aug '16

17 Aug '16

Hi. I have connected probe 10973 (which was offline several years) to the network. Firmware updated from 3.3.8 to 4010. "Status" said that "Your probe is currently connected." But on probe page i see the message: "Note: this probe is most likely not operational, and as such it has been written off as of 2013-12-03 15:44 UTC. The most likely reason for this is that the host could not be contacted." It is ok? :) Do i need to upgrade FW to latest version (tried to reboot probe several times, but fw version still 4010)? Sent via RIPE Forum -- https://www.ripe.net/participate/mail/forum

2 1

RIPE Atlas "Commercial use" policy
by Robert Kisteleki 17 Aug '16

17 Aug '16

Dear colleagues, A few different organisations have approached us about using RIPE Atlas data for commercial products, services, reports, etc. We’ve now published conditions for the commercial use of RIPE Atlas data: https://atlas.ripe.net/get-involved/commercial-use/ Please read these conditions carefully if you plan on using RIPE Atlas data for any commercial purpose, and don’t hesitate to contact us if you have any questions. Regards, Robert Kisteleki RIPE NCC

1 0

Alternative to jq: gron
by Stephane Bortzmeyer 16 Aug '16

16 Aug '16

It seems many people here use jq to browse JSON files. I've been referred recently to gron <https://github.com/tomnomnom/gron> which is quite different: less features but probably simpler to use for beginners. Unlike jq, gron does not have a filtering language: it just formats the JSON in a way that makes simple to use traditional grep. Here is an example with measurement #4477822, a DNS one: % gron 4477822.json|more json = []; json[0] = {}; json[0].from = "178.248.214.8"; json[0].fw = 4730; json[0].group_id = 4477822; json[0].lts = 18; ... Selecting the values of the serial number is as simple as: % gron 4477822.json | grep SERIAL json[0].resultset[0].result.answers[0].SERIAL = 2223898795; json[0].resultset[1].result.answers[0].SERIAL = 2223898793; json[1].resultset[0].result.answers[0].SERIAL = 2223898790; json[1].resultset[1].result.answers[0].SERIAL = 2223898792; json[1].resultset[2].result.answers[0].SERIAL = 2223898795; json[2].resultset[0].result.answers[0].SERIAL = 2223898791; ... And you can turn back the result of the filtering into JSON.

2 1

Probe down - USB?
by İhsan Doğan 13 Aug '16

13 Aug '16

Hi, My probe went down this morning. Probably I'm running into the issue with the USB stick. I was thinking to replace the USB stick. Are there any special requirements (size, speed, etc.) for the USB stick? -Ihsan -- ihsan(a)dogan.ch http://blog.dogan.ch/

3 4

Re: [atlas] Probe down - USB?
by Colin Johnston 13 Aug '16

13 Aug '16

or mount the usb flash with linux ext3 and fsck check it :) Sent from my iPhone > On 13 Aug 2016, at 13:44, Budiwijaya <budiwijaya(a)ipv6.or.id> wrote: > > You don't need to change the USB stick, just unplug from the probe, > format the disk with fat32 using PC, plug back again to the probe, > and you're done. > > Thank you > Budiwijaya > > > On Sat, Aug 13, 2016 at 6:24 PM, =C4=B0hsan=C2=A0Do=C4=9Fan <ihsan(a)dogan.ch= >> wrote: >> Hi, >> >>> On Saturday, 13 Aug 2016 11:00 +0200, Estelmann, Christian wrote: >>> >>> every USB flash drive with 4 GB (or more) will do. >>> See >>> https://labs.ripe.net/Members/philip_homburg/troubleshooting-ripe-atlas-= > probes-usb-sticks >> >> Thanks. I have now ordered a 8 GB flash drive. >> >>> Don't forget that all data on the flash drive will be destroyed. >> >> But it's not affecting me, as it's pulling the configuration >> again, right? >> >> >> >> -Ihsan >> >> -- >> ihsan(a)dogan.ch http://blog.dogan.ch/ >

1 0

IPv4-only Anchors Now Supported
by Robert Kisteleki 12 Aug '16

12 Aug '16

Dear colleagues, We've decided to support "IPv4-only" anchors in ASNs where IPv6 is not available. You can learn more in this RIPE Labs article: https://labs.ripe.net/Members/suzanne_taylor_muzzin/ipv4-only-ripe-atlas-an… Regards, Robert Kisteleki RIPE NCC

6 5

Incrementing LTS For probe 6106
by Clinton Work 09 Aug '16

09 Aug '16

Probe 6106 has an LTS value of at least 187450 and it continues to grow. ================================= Clinton Work Senior Design Specialist IP Core Network Integrity TELUS | Network and System Operations Phone: (403) 384-4027

2 1

Awarding credits for measurement results
by Robert Kisteleki 04 Aug '16

04 Aug '16

Dear probe and anchor hosts, When you create measurement results in RIPE Atlas, you’ll now get a little something extra back in the form of credits. From now on, we’re giving all RIPE Atlas probe and anchor hosts one credit back for every measurement result they generate. This means that most probe hosts will earn up to an additional 10,000 credits (50%) per day on top of the credits they get for keeping their probes online, anchor hosts will earn an additional roughly 200,000 credits (100%) daily, and DNSMON anchor hosts will receive roughly 1,000,000 additional credits. This is our way of rewarding the probe and anchor hosts who contribute the most to RIPE Atlas - enjoy! Regards, Robert Kisteleki RIPE NCC

2 1

Verbatim stick falled in read only
by Francesco Molitierno 04 Aug '16

04 Aug '16

The verbatim stick of my probe seems falled in a read-only state, there is something that i can try to fix?

2 1

Probe reported as disconnected but is actually online
by Boris Fersing 04 Aug '16

04 Aug '16

Hi there, Today I had a power failure at home and since then, my probe's state is "disconnected", but I checked the network traffic and it looks like the probe is actually able to reach the internet and is doing some DNS requests I don't know about: U431.M<PROBES MAC>.sos.atlas.ripe.net U980.M<PROBES MAC>.sos.atlas.ripe.net U116.M<PROBES MAC>.sos.atlas.ripe.net Do you know what those SOS requests mean? The SOS history on the atlas.ripe.net page doesn't show any useful message. The Status (beta) tab shows the following message: ===== Firewall Problems Suspected What does this mean? Probes connect to the controlling infrastructure using SSH (via port 443). If our system detects that the probe is successfully engaged in other kinds of activities, but these SSH connections fail, then it's highly likely that these connections are somehow blocked or disturbed. This could be because there's a firewall blocking these connections. Another reason could be that there is a (transparent) proxy in the way that affects port 443 (usually HTTPS) connections, which means the probe and its controller cannot mutually authenticate each other (because the proxy is interfering). How can I fix this? Check whether you have a firewall or an aggressive NAT appliance preventing such connections. Also check whether there's a transparent proxy on the path. Alternatively, you can try plugging in the probe on a different network to confirm whether a firewall / proxy is really causing the problem. ===== But since I don't know which host the probe is trying to connect to, I can't really test it and tcpdump doesn't show any attempt to a port 443. Thanks Boris

4 4

atlas-stream SSL problem
by Massimo Candela 03 Aug '16

03 Aug '16

Hi all, We are currently experiencing an issue with the load balancer of the streaming service over SSL. We are working on it. The service on http on port 80 is not affected. The Atlas CLI and Cousteau are not affected too. Sorry for the inconvenience. It will be fixed soon. Best regards, Massimo Candela

1 1

New analysis of version 3 probes on RIPE Labs
by Philip Homburg 02 Aug '16

02 Aug '16

Hi, As promised, we’ve continued to look into the issue that some people are having with the version 3 probes and have found that actual hardware failures for version 3 probes are in fact relatively rare compared to filesystem corruption. We’ve published a new article on RIPE Labs with the complete analysis: https://labs.ripe.net/Members/philip_homburg/further-analysis-of-ripe-atlas… We’ll continue looking into these issues, so stay tuned for future articles. Philip Homburg RIPE NCC

1 0

Re: [atlas] Troubleshooting USB stick issues - reaching out
by Christophe Van Reeth 28 Jul '16

28 Jul '16

Hi, It's not just the Sandisk sticks that go into permanent readonly mode. The Verbatim have the same problem. Mine went into readonly mode after only 10.5 months of service. Kind regards, Christophe Van Reeth > Dear colleagues, > > recently, some of the third version of RIPE Atlas probes have had an > issue with their USB sticks. > > We're still investigating what may be causing this issue, > and in the meantime we have a possible solution, outlined in this RIPE > Labs article (and below in the email) > https://labs.ripe.net/Members/philip_homburg/troubleshooting-ripe-atlas-pro… > > These steps might not be a surprise to the users on this list, > but on the 4th of July we reached out to almost 5000 hosts of > "abandoned" probes, and we see immediate positive results! > > As you can see from some screenshots I quickly made, > number of active probes have increased - from 8883 on 1st July, > to 9323 this morning. Allowing for normal fluctuations, > this is still a considerable increase -- and we are grateful! > > Thank you for all the effort that you put into keeping the > RIPE Atlas network strong by keeping your probes connected. > > Kind regards, > Vesna (and the RIPE Atlas team) > > === > > Steps to power-cycle probe without USB stick: > > 1. Unplug the probe from its power source > 2. Remove the USB stick from the probe > 3. Plug in the probe WITHOUT the USB stick > 4. Wait for ten minutes > 5. Insert the USB stick > > After an hour, check SOS-messages & "Status" tab > > Note: Only on a network with working DHCP. > If you have configured probe to use static IP, > this setting would be lost if trying the steps. > > If this didn't help, try using a new, brand-name USB stick that is at > least 4GB in size (it does not need any preparation but its contents > will be erased so make sure it does not store anything crucial) > > If the problem is still there, please contact us at atlas(a)ripe.net >

1 0

Fwd: Probe 2317 is down (home fibre)
by Colin Johnston 25 Jul '16

25 Jul '16

seems fine to me ? dont have connectivity to ripe site though from BT network range in uk what is telia upto ? Colins-iMac:~ colinj$ traceroute www.ripe.net traceroute to www.ripe.net (193.0.6.139), 64 hops max, 52 byte packets 1 bthomehub (192.168.1.254) 1.913 ms 1.078 ms 1.078 ms 2 * * * 3 * * * 4 31.55.185.196 (31.55.185.196) 16.187 ms 15.477 ms 15.443 ms 5 195.99.127.142 (195.99.127.142) 15.557 ms 195.99.127.130 (195.99.127.130) 16.274 ms 195.99.127.128 (195.99.127.128) 16.602 ms 6 vhsaccess2-pos1-0.faraday.fixed.bt.net (195.99.127.9) 16.979 ms 16.611 ms 195.99.127.25 (195.99.127.25) 17.097 ms 7 166-49-211-240.eu.bt.net (166.49.211.240) 16.413 ms 166-49-211-236.eu.bt.net (166.49.211.236) 16.225 ms 166-49-211-238.eu.bt.net (166.49.211.238) 15.821 ms 8 213.248.82.249 (213.248.82.249) 16.880 ms 15.785 ms 15.470 ms 9 ldn-bb2-link.telia.net (62.115.137.194) 16.633 ms 213.248.82.249 (213.248.82.249) 15.631 ms 15.400 ms 10 ldn-bb3-link.telia.net (80.91.248.90) 15.776 ms ldn-bb2-link.telia.net (213.155.136.62) 16.815 ms adm-bb4-link.telia.net (62.115.142.221) 22.936 ms 11 adm-b2-link.telia.net (62.115.141.51) 25.759 ms adm-b2-link.telia.net (80.91.253.182) 22.263 ms adm-b2-link.telia.net (62.115.141.17) 21.979 ms 12 adm-b2-link.telia.net (80.91.253.182) 22.481 ms adm-b2-link.telia.net (62.115.141.9) 22.344 ms adm-b2-link.telia.net (62.115.141.63) 27.606 ms Colin > Begin forwarded message: > > From: RIPE Atlas (no reply) <no-reply(a)ripe.net> > Subject: Probe 2317 is down (home fibre) > Date: 21 June 2015 20:30:07 BST > To: colinj(a)mx5.org.uk > > Dear Dear colin johnston, > > Your probe 2317 has been disconnected since 2015-06-21 18:49:16 UTC. > > This is an automatically generated email from RIPE Atlas. It was sent to you because you asked to be notified if your probe becomes disconnected for more than 30 minutes. > > If you want to change this, or disable this notification altogether, please go to https://atlas.ripe.net/probes/2317/, and click the "edit" button under "Notifications". > > Kind regards, > > RIPE Atlas Team > atlas(a)ripe.net

5 7

Identifying widespread outages using atlas?
by Rafal.Jankowski＠thomsonreuters.com 20 Jul '16

20 Jul '16

Hi I'm wondering if there is any good statistic tool that helps identyfing any widespread Internet outages using ripe atlas probes such as ISP issues (like todays http://www.bbc.co.uk/news/technology-36844712) cable cuts, etc. Normally I select probe and look into public measurements but it does not seem to be very effective. ________________________________ This e-mail is for the sole use of the intended recipient and contains information that may be privileged and/or confidential. If you are not an intended recipient, please notify the sender by return e-mail and delete this e-mail and any attachments. Certain required legal entity disclosures can be accessed on our website.<http://site.thomsonreuters.com/site/disclosures/>

2 3

Stop time not retained when creating new measurement
by Bill Fenner 18 Jul '16

18 Jul '16

Hi, I created a new measurement this morning, https://atlas.ripe.net/measurements/4467029/ . Its status says: Timing 2016-07-16 07:35 No stop time defined but I filled in the stop time when I created the measurement via the web page; I saved the command that it gave me to invoke the API and it includes: ... "is_oneoff": false, "bill_to": "fenner(a)fenron.com", "stop_time": 1469361631 } a) this feels like a bug. Is it a bug? b) can I add the stop time post-facto, or should I remember to go back and click "stop"? Thanks, Bill

2 1

start one-off from probe overview page
by Job Snijders 15 Jul '16

15 Jul '16

Hi all, UI feature requests: It would be cool if there is a button to start a one-off measurement from a certain probe's overview pages. If I am at https://atlas.ripe.net/probes/25606/ - would be nice if I can immediately jump into a one-off, rather then copy-pasting the probe's ID and creating a new one-off UDM. Kind regards, Job

1 0

Error creating one-off ping measurement
by Jared Mauch 15 Jul '16

15 Jul '16

We are attempting to test some things and I’m getting this error. "A one-off measurement cannot have the interval field set” It seems to be a problem if this field is even blank, anyone else experience this? - Jared

3 3

Re: [atlas] Is the Atlas probe hackable?
by fuller＠beif.de 14 Jul '16

14 Jul '16

related to? http://mailman.nanog.org/pipermail/nanog/2016-March/084946.html

1 0

Probe down
by Виталий Туровец 14 Jul '16

14 Jul '16

Hello there! I've got a probe #20190 (https://atlas.ripe.net/probes/20190/) and it shows disconnected status it Atlas Web UI. I've tried to reboot the probe, it gets the IP address from my router via DHCP and i can ping it, the probe opens TCP connection to 193.0.19.25:443 and that's it. The question: how do i make it connect to Atlas again? -- ~~~ WBR, Vitalii Turovets Software Engineer VITU-RIPE

2 1

Result streams not working
by Florencia Alvarez Etcheverry 13 Jul '16

13 Jul '16

Hello, I started working with RIPE Atlas last week, when I made a script to create a one-off ping measurement between two specific probes (which I ping to check if they were working). I used Cousteau API, by default I sent 3 packets and I had 5 seconds of timeout. I got the results one time and then it stopped working. I changed the timeout to 3 or 4 minutes and while waiting for the callback function to execute I checked on the webpage and I can see the results for every measure I launched. So I see the results on the page but they don't get to the stream and the callback function is never called. I also saw the status changed from "ongoing" to "stopped" several minutes after I've seen the results; which leads me to another question, when a measurement stops?, why if I already have the results of a ping (that is the only thing I've launched) it's still running? I tried with Cousteau and also directly with socketIO but it has the same behavior. When I took off the parameters "packets=1,interval=60" of the request (leaving default values), I got the result with Cousteau API, but not with the socket directly. When I run it again it didn't work, so it looks like it works one of 20 times. Is there something I could do or am I doing something wrong? Thank you, Florencia. Sent via RIPE Forum -- https://www.ripe.net/participate/mail/forum

2 6

Troubleshooting USB stick issues - reaching out
by Vesna Manojlovic 11 Jul '16

11 Jul '16

Dear colleagues, recently, some of the third version of RIPE Atlas probes have had an issue with their USB sticks. We're still investigating what may be causing this issue, and in the meantime we have a possible solution, outlined in this RIPE Labs article (and below in the email) https://labs.ripe.net/Members/philip_homburg/troubleshooting-ripe-atlas-pro… These steps might not be a surprise to the users on this list, but on the 4th of July we reached out to almost 5000 hosts of "abandoned" probes, and we see immediate positive results! As you can see from some screenshots I quickly made, number of active probes have increased - from 8883 on 1st July, to 9323 this morning. Allowing for normal fluctuations, this is still a considerable increase -- and we are grateful! Thank you for all the effort that you put into keeping the RIPE Atlas network strong by keeping your probes connected. Kind regards, Vesna (and the RIPE Atlas team) === Steps to power-cycle probe without USB stick: 1. Unplug the probe from its power source 2. Remove the USB stick from the probe 3. Plug in the probe WITHOUT the USB stick 4. Wait for ten minutes 5. Insert the USB stick After an hour, check SOS-messages & "Status" tab Note: Only on a network with working DHCP. If you have configured probe to use static IP, this setting would be lost if trying the steps. If this didn't help, try using a new, brand-name USB stick that is at least 4GB in size (it does not need any preparation but its contents will be erased so make sure it does not store anything crucial) If the problem is still there, please contact us at atlas(a)ripe.net

3 2

sometimes no RTT?
by Antranig Vartanian 08 Jul '16

08 Jul '16

Hi all! I'm new to RIPE Atlas, and right now using it for educational purposes :)) lately I've seen that some of my traceroute measurements do not have RTT. although it's not completely ignored by the hop (I get the data like from, size, ttl), but only rtt is missing :)) any idea how, why and when does this happen? :) for a live example, check Measurement #4458653. 48th probe's 11th hop's 1st query (counting from zero, btw) does not have rtt :) thanks in advance! side question: is there an (un)official IRC channel? :) -- Antranig Vartanian | PGP Key ID : 0xDAB81456 https://antranigv.am | https://cert.am (* do one thing and do it well *)

3 8

development server?
by Ollivier Robert 06 Jul '16

06 Jul '16

Hello, I've been hosting a probe for quite sometimes and now that APIv2 is out, I've writing a Go library to access it. Is there a development server I could hit instead of the regular one in order to clutter the DB with temporary/trash measurements? Thanks. -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto(a)keltia.net In memoriam to Ondine, our 2nd child: http://ondine.keltia.net/

3 2

Is the Atlas probe hackable?
by Hank Nussbacher 06 Jul '16

06 Jul '16

I received a report from one of our security monitoring systems about one of our probes (#17846) - https://atlas.ripe.net/probes/17846/ which appears to be infected with Tinba: > Security incident #1 - Tinba infection > Involved internal Hosts: > atlas-probe.cc.biu.ac.il 132.70.248.150 spotted since > 2016-06-30 > 23:58:54 till 2016-07-01 05:01:20 > Malicious activities found: > Tinba infection > related indication of compromise: > Communication with CnC > 192.112.36.4 > 192.203.230.10 > 192.228.79.201 > 192.33.4.12 > 192.36.148.17 > 193.0.14.129 > 198.41.0.4 > 198.97.190.53 > 199.7.83.42 > 199.7.91.13 > 202.12.27.33 Should we be worried? Thanks, Hank

4 4

Is there something up with atlas.ripe.net at the moment ?
by Steve Pointer 05 Jul '16

05 Jul '16

Hi I am trying to add a couple of new measurements, however it has been "...calculating" for about an hour now. Is there a known issue? Many Thanks Steve P -- Steve Pointer spointer(a)humdai.net

2 2

SSL Measurement shows time errors for Certs
by Paul van der Zwan 29 Jun '16

29 Jun '16

I have just created an SSL measurement with 20 probes and they all show the following error for the cert validity dates: Invalid date UTC . AFAIK the cert contains valid dates.. Any idea ? Thanks, Paul Sent via RIPE Forum -- https://www.ripe.net/participate/mail/forum

1 0

RIPE NCC Webinars - new dates
by Vesna Manojlovic 29 Jun '16

29 Jun '16

Dear colleagues, If you are interested in a RIPE Atlas webinar: - new date for summer is announced: 16.8. (below) - description & additional material is available here: https://www.ripe.net/support/training/learn-online/webinars/advanced-ripe-a… You can register on-line if you are an LIR; otherwise, please contact <training(a)ripe.net>. Regards, Vesna -------- Forwarded Message -------- Subject: [ncc-announce] [training] RIPE NCC Webinars - new dates Dear colleagues, We are pleased to announce the launch of new dates for our Webinars. The RIPE NCC Webinars are live and take only one hour. You can interact with our trainers without leaving your desk. We focus on the topics and issues most important for LIRs. Register now at https://www.ripe.net/support/training/learn-online/webinars Participation is limited to 20 people, so don't hesitate if you want to take part! If you have questions, please email <training(a)ripe.net>. We look forward to seeing you online. Kind regards, RIPE NCC Training Service

1 0

More than 200 RIPE Atlas anchors now online
by Michela Galante 29 Jun '16

29 Jun '16

Dear colleagues, Thanks to thirteen new RIPE Atlas anchors being activated over the last two months, we have now reached an important milestone: more than 200 anchors online! Learn more about what anchor measurements can do for you: https://atlas.ripe.net/anchors/about/ We have also started decommissioning anchors with older hardware and working with hosts to replace them with updated hardware. We'd like to thank Nick Hilliard for helping us test our decommissioning procedure and becoming the first anchor host to update to the new hardware for as2128, hosted by INEX in Dublin, Ireland. Since our last announcement, the following anchors have become active: - cz-brq-as24971, hosted by Master Internet s.ro.o in Brno, Czech Republic - nl-ams-as1200, hosted by AMS-IX B.V. in Amsterdam, Netherlands - ca-wtl-as4508, hosted by NeuStyle Corporation in Waterloo, Canada - ie-ork-as2128, second anchor for INEX, hosted in Cork, Ireland - lv-rix-as52048, hosted by DATACLUB S.A. in Riga, Latvia - dk-taa-as51468, hosted by One.com in Tastrup, Denmark - ie-dub-as2128, hosted by INEX in Dublin, Ireland (replaces older hardware) - us-rno-as3851, hosted by University of Nevada in Reno, United States - nl-dft-as31019, hosted by Meanie in Delft, Netherlands - ru-mot-as13238, hosted by Yandex LLC in Mytishchi, Russia - de-bwe-as680, hosted by TU Braunschweig, Gauss-IT-Zentrum in Braunschweig, Germany - nl-ams-as35733, hosted by EURid VZW in Amsterdam, Netherlands - us-abn-as51468, hosted by One.com in Ashburn, United States - kh-pnh-as7712, hosted by Sabay Digital Coperation (sponsored by APNIC) in Phnom Penh, Cambodia The map of all anchor locations is available at: https://atlas.ripe.net/anchors/map/ You can access the anchoring measurements for all anchors at: https://atlas.ripe.net/anchors/list/ And here are all of the anchor hosts: https://atlas.ripe.net/get-involved/community/#!tab-anchor-sponsors We are still accepting new applications from organisations interested in hosting a RIPE Atlas anchor, and are particularly interested in deploying anchors in the Middle East, Western Asia, Latin America and Africa in order to add more geographical diversity to the measurement data. To apply for your own RIPE Atlas anchor, please visit: https://atlas.ripe.net/get-involved/become-an-anchor-host/ It’s also possible to sponsor an anchor for organisations that want to host one but don’t have the necessary funding. To learn more about sponsoring an anchor, please contact us at atlas(a)ripe.net Regards, Michela Galante Measurements Community Building RIPE NCC

1 0

written off Probe #20578
by FREDDY BULOW 28 Jun '16

28 Jun '16

hello, is it gonna be my probe on, I just received the probe. because I have this message on the interface of the count : Note: this probe is Most Likely not operational, and hast Such it has-been written off as of 2015-05-27 1:02 UTC. The Most Likely reason for this is que le host couldn't be contacted. Thank you for your help. Sent via RIPE Forum -- https://www.ripe.net/participate/mail/forum

2 1

accounting glitch for probe 15105
by Kasper Pedersen 28 Jun '16

28 Jun '16

Tonight Freddy Bulow's post made me take a look at 15105. I was certain it would be up, but that was only halfway what I found. It was listed as being down since June 16th, and the uptime graph was showing an 8-day hole. It was, however, showing traffic on the graph, and locally I was also seeing normal probe traffic. Here's a pcap: https://highlyexperimental.kitsune.dk/201606242131.pcap At packet 765 I powercycled the probe, it came back up, and now showed 0 minutes up. That was expected, but what also happened was that the uptime graph filled in to no longer show downtime, the log entry showing the probe going down on the 16th disappeared (yes, really), and a new one showed it going down on the 24th with a few seconds downtime. The only thing left is the 8-day hole in the credit log, that did not change. /Kasper Pedersen Beware of corner cases. They tend to have sharp corners. Sent via RIPE Forum -- https://www.ripe.net/participate/mail/forum

2 1

How to get a new USB stick ?
by Élodie de FranceServ Hébergement 27 Jun '16

27 Jun '16

Hello, The SanDisk USB (4GB) provided with the RIPE Atlas probe don’t work anymore since more 5 days and the connection logs say “NO USB”. To check the USB stick, I plugged a personal one and since this time the probe is working again. I have this probe number 18685 since 2015-03-05. I would like know if the team could send me a new USB stick to replace the old one please or if I need to buy a new one myself ? Best regards, Élodie

5 4

Probe #16917 shows disconnected
by Jacques Lav!gnotte. 22 Jun '16

22 Jun '16

Hi RIPE-Atlas-Probe-16917 gets the Adresse IP : 192.168.1.13 on the DHCP of the ADSL Modem but RipeAtlas site says probe is disconnected. I restarted it several times, checked the cable to the witch and replaced the power supply. No way : The 'globe' LED is permanently blinking. What else should I check ? Thanks, Jacques -- GnuPg : C8F5B1E3 WeUsePGP Because privacy matters http://weusepgp.info/

3 6