- ripe-atlas - mailman.ripe.net

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