February 2016 - ripe-atlas - mailman.ripe.net

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

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

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

02 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

Failing 4GB USB on v3 probes?
by Phillip Remaker 11 Apr '16

11 Apr '16

So far, I have had two of the SanDisk Cruzer 4GB drives (SDCZ33) fail, and I think I have two other ML-3020 (v3) devices with the same fate. Case #1, the drive fell into read only one. Case #2, the drive identifies to the USB, but read of block 0 (capacity) fails. The first time I called SanDisk and jumped through their hundred hoops to replace it.They were reluctant since I couldn't produce a receipt. This time, I just grabbed an old 8GB USB and dropped it in. Looks like it only uses 3GB. Does Atlas plan to pursue warranty claim, or is this an acceptable failure level for the probes?

2 1

Scheduling a test for all probes?
by Jared Mauch 06 Apr '16

06 Apr '16

Is there a way to schedule a one-off test on all the probes to be run “at a leisurely pace”, eg: looking up a specific DNS QNAME? (I’ll call it a lazy query/scheduling). - Jared

3 2

probe tagged as "system: Firewall problem suspected"
by sarah.wassermann＠student.ulg.ac.be 02 Apr '16

02 Apr '16

Hi, I have (once again) problems with my probe (probeID: 24102). This time, it got tagged as "system: Firewall problem suspected". The strange thing is that I did not touch anything on my router when this happened and did not change any other configuration... This probe is located in Luxembourg. I now brought it to Belgium and plugged it into the router I have here. Nothing changed. Furthermore, here in Belgium, its 3rd light is slowly blinking, which let's suppose that it gets tuck in the network-testing phase. Anybody knows how to fix this? (I already had some problems with that probe ("system: Hardware problem suspected") but I could solve them thanks to a hint given by a user.) My worst problem is that, due to this issue, we have difficulties earning enough credits for our research... So I would be really happy if this problem could be solved easily :( Thanks! Sarah

4 8

Implementing structured error reports ("Problem Details for HTTP APIs")?
by Stephane Bortzmeyer 01 Apr '16

01 Apr '16

Hello, IETF approved the future RFC draft-ietf-appsawg-http-problem "Problem Details for HTTP APIs" which standardize structured error reports (in JSON) to add machine-readable information to HTTP error codes. Would it be a good idea to convert current Atlas reports ({"error":{"status":400,"code":104,"detail":"__all__: Your selected prefix is not covered by our network.","title":"Bad Request"}}) to the new and standard format?

3 4

Querying your own measurements
by Sebastian Castro 09 Mar '16

09 Mar '16

Hi: I'm currently testing the API to get a list of my own measurements. The API here reports ----------- Querying for Your Own Measurements In order to limit the results to your measurements only, just add a mine=true argument. For example: /api/v1/measurement/?mine=true Note that this only works if you're logged in, otherwise the result is the same as for any unauthenticated user. ----------- This seems to imply you need to manage a session within your code to get your own measurements, which I think violates the principle of a REST API. If you have the API key that provides you with access, shouldn't be reasonable to run the call as /api/v1/measurement/?mine=true&key=API_KEY and get a list of your own measurements? Thoughts? Am I reading the documentation in the wrong way? Thanks in advance -- Sebastian Castro Technical Research Manager NZRS Ltd. desk: +64 4 495 2337 mobile: +64 21 400535

9 17

Ping option DF
by dave 29 Feb '16

29 Feb '16

Hi, It seems atlas sends out ping with fragmentation allowed. Why is there no option to enable DF? Thanks, Dave.

2 1

Thirteen new RIPE Atlas anchors have joined the community
by Michela Galante 18 Feb '16

18 Feb '16

Dear RIPE Atlas users, 13 new RIPE Atlas anchors have been activated during the last month and a half bringing the total number to 177. - id-jkt-as10208, hosted by PT. Millenium Internetindo in Jakarta, Indonesia and sponsored by APNIC. - ar-bue-as4270, hosted by ARIU in Buenos Aires, Argentina and sponsored by LACNIC. - de-nue-as60574, hosted by net-manager UG in Nuremberg, Germany. - uk-boh-as196745, hosted by Datacenta Hosting in Bournemouth, United Kingdom. - at-vie-as30971, hosted by nic.at in Vienna, Austria. - uk-lon-as6908, hosted by Six Degrees Group in London, United Kingdom. - nl-utc-as1103, second anchor hosted by SURFnet, in Utrecht, Netherlands. - Two anchors hosted by INX-ZA/Internet Service Providers' Association of South Africa: za-jnb-as37474 in Johannesburg and za-umr-as37668 in Umhlanga, South Africa. - ru-led-as43317, hosted by Fishnet Communications in Saint Petersburg, Russia. - nl-dro-as12414, hosted by Solcon Internetdiensten N.V. in Dronten, Netherlands - de-drs-as42699, hosted by managedhosting.de GmbH in Dresden, Germany. - fo-hyv-as15389, hosted by P/F Telefonverkid in Hoyvik, Faroe Islands. 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 the logos and links to hosting companies: 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. 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 more organisations that want to host a RIPE Atlas anchor but don’t have the necessary funding. To learn more about sponsoring an anchor, please contact us at mcb(a)ripe.net To apply for your own RIPE Atlas anchor: https://atlas.ripe.net/get-involved/become-an-anchor-host/ For any other questions, please contact us at atlas(a)ripe.net Regards, Michela Galante Measurements Community Building RIPE NCC

1 0