August 2016 - ripe-atlas - mailman.ripe.net

Plan to Implement RIPE Atlas WiFi Measurements
by Robert Kisteleki 09 Oct '17

09 Oct '17

Dear colleagues, We wanted to update the community and let you know that we plan to start work on the proposed experiment with WiFi measurements in mid-2016. As we communicated in a recent RIPE Labs article, we will work with GÉANT as a test partner to learn more about the operational effects of introducing WiFi measurements to the RIPE Atlas system, in addition to the benefits we believe this could provide for the entire RIPE Atlas community. Please see the article for more details if you are interested: https://labs.ripe.net/Members/suzanne_taylor_muzzin/ripe-atlas-wifi-measure… We will continue to update you once we’ve begun work on this plan, and we welcome your comments in the meantime. Regards, Robert Kisteleki RIPE NCC

3 3

RIPE Atlas Interface Hackathon, 21-22 May, Copenhagen
by Vesna Manojlovic 23 Jan '17

23 Jan '17

Dear colleagues, Calling all front-end developers, UI designers, network operators and other enthusiastic coders! The next RIPE Atlas hackathon takes place 21-22 May in Copenhagen, the weekend before the RIPE 72 Meeting. We're looking for creative thinkers to help us develop new interfaces for RIPE Atlas. All source code developed during the hackathon will be publicly licensed and available on GitHub, and will be free for the entire community to use. -------------------- How to Apply -------------------- Interested? Learn more and apply online today! https://atlas.ripe.net/hackathon/Interface/?pk_campaign=hackathon&pk_kwd=li… *The application deadline is 23 March* Please note that we are unfortunately unable to provide travel or accommodation funding. We look forward to seeing you there! Regards, Vesna and the RIPE Atlas Team

1 4

Probe marked as offline, but it's online...
by Christian Schrötter 10 Nov '16

10 Nov '16

Hello Atlas users! I've connected my probe to a new network environment, to test everything before the big migration starts. It came up again immediately and displayed it's new network details at the WebUI. For the first time there was an IPv6-ULA prefix visible. The router (OpenWrt 15.05) supports full IPv6 via tunnel, but it's not advertised to the probe's VLAN and blocked by firewall rules. Everything seems to work, good! I've switched it off/on for several times, went back to the old router/modem and powered it on again. After some hours I've checked the WebUI again: My probe is offline! :-( I've tested it again on the new router: Offline! Once again on the old setup: Offline! Untouched default router/modem from my ISP: Offline! Current LED status: (from 1-5; power to button) > on > off > slow blink > on > on SOS-DNS-history from Wireshark: (switch port mirrored to my analysis interface) > Standard query 0x0002 AAAA U.*************.sos.atlas.ripe.net > Standard query response 0x0002 AAAA 2001:67c:2e8:11::c100:1337 > Standard query 0x0003 A U.*************.sos.atlas.ripe.net > Standard query response 0x0003 A 193.0.19.55 The probe is online and communicates with many servers. Looks like the built-in tests are running fine. There is NTP, DNS, ICMP, UDP and HTTP traffic. But it's still offline at the WebUI. I've double and triple checked everything on my side. Any ideas what's going wrong? -- With kind regards, Christian Schrötter

2 4

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

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