March 2016 - ripe-atlas - mailman.ripe.net

IPv6 working
by gboonie 30 Mar '16

30 Mar '16

Hi, This seems to be an anchor that has Ipv6 connectivity but probably connected to a network with a incomplete routing table. https://atlas.ripe.net/probes/6149/#!tab-builtins It cannot reach a lot of the internet so I'm wondering what causes the system to flag it as "ipv6 works". Also, I've done a few hundred pings and found that probes get their "ipv6 works" only taken away after it has been failing for a few hours. Could that please be changed to something short like 10 minutes? And if possible, some stability tests so that if connectivity comes and goes that if does not get back it's "works" status. Thanks, Dave

4 4

Re: [atlas] Probe not flagged as "IPv4 works"
by gboonie 24 Mar '16

24 Mar '16

Hi Philip, A powercycle did not help. I did a reboot without USB stick and formated it in my laptop. Then plugged it back and after some minutes it started working again. Some googeling showed that the stick can be replaced by a 4GB stick but the one that it currently has seemed to be only 1GB. What is your view on this? The other strange thing is that the probe did somehow earn credits. That seems to contradict that it was down. On the other hand the "Connection and traffic" graph clearly shows that it is up after been down. Thanks, Dave Op 23-3-2016 om 16:29 schreef Philip Homburg: > On 2016/03/23 16:27 , Dave . wrote: >> Dit you remotely order a reboot?I did get the mail that the probe is >> down now. > Yes, I did. It is now connected again, but doesn't really work. > >> I'll power cycle when I get home and if it does not help, I'll do te >> delayed plug in trick. > That would be nice. > > Philip >

2 1

Probe not flagged as "IPv4 works"
by gboonie 23 Mar '16

23 Mar '16

Hi, I have 3 probes in different networks. This one probe is not selected for tests when I do a test on multiple probes that I select op probe ID or ASN. This is the troubling probe: https://atlas.ripe.net/probes/24645/ It is connected via a 4G LTE router. The router is up and everything else works. I could just reboot the modem and the probe but I'm wondering why it fails to get flagged with "IPv4 works". The "built in" test seem to work fine. What could be the issue? Is there something I could do to debug? Or just reboot and forget about it? Thanks, Dave

2 1

Fwd: New on RIPE Labs: Support for Elliptic Curve Cryptography (ECC) in DNS Resolvers as Seen by RIPE Atlas
by Vesna Manojlovic 21 Mar '16

21 Mar '16

Dear colleagues, Please find this new article on RIPE Labs contributed by Maciej Andzinski: The Elliptic Curve Cryptography (ECC) is becoming increasingly popular in DNSSEC. While it is sometimes considered to be a remedy for the low DNSSEC adoption rate, there is also a lot of controversy around it. One of the main concerns is that DNSSEC-validating resolvers don't always make use of ECC. We used RIPE Atlas to measure the support for ECC in DNS resolvers. https://labs.ripe.net/Members/maciej_andzinski_2/support-for-elliptic-curve… Kind regards, Vesna Manojlovic RIPE NCC

1 0

Eleven new RIPE Atlas anchors have joined the community
by Vesna Manojlovic 18 Mar '16

18 Mar '16

Dear colleagues, 11 new RIPE Atlas anchors have been activated during the last month, bringing the total number to 188: - uk-lba-as33920, hosted by aql in Leeds, United Kingdom - de-ber-as62310, hosted by managedhosting.de GmbH in Berlin, Germany - bt-thi-as38740, hosted by Tashi InfoComm Limited in Thimpbu, Bhutan and sponsored by APNIC - cz-prg-as52130, hosted by Livesport s.r.o. in Prague, Czech Republic - de-dar-as8365, hosted by TU Darmstadt - Secure Mobile Networking Lab/ DFG Collaborative Research Center in Darmstadt, Germany - one more anchor hosted by INX-ZA/Internet Service Providers' Association of South Africa: za-cpt-as37663 in Cape Town, South Africa - ee-tll-as51349, by Estonian Internet Foundation in Tallinn, Estonia - two anchors hosted by Sky UK Limited: uk-lon-as5607 in London and uk-slo-as5607 in Slough, United Kingdom - sixth anchor for Leaseweb Network B.V.: hk-hkg-as133752 in Hong Kong - fi-hel-as3274, hosted by Cygate Oy in Helsinki, Finland. 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, Vesna Manojlovic Measurements Community Building RIPE NCC

1 0

Webinar "Advanced RIPE Atlas Usage" on Thursday 17 March
by Michela Galante 15 Mar '16

15 Mar '16

Dear colleagues, On Thursday 17 March, 12:30 UTC, we are hosting the webinar on "Advanced RIPE Atlas Usage", aiming to teach network operators how to use RIPE Atlas measurements for network monitoring and troubleshooting. Register now at: https://lirportal.ripe.net/training/register/courseCode/WEB20160011 Web-registration is *only* possible for LIRs (RIPE NCC members). Non-members of RIPE NCC (people who do not have "Reg-ID") can email training(a)ripe.net and be manually registered. More details below. -------------------------- https://www.ripe.net/support/training/learn-online/webinars/advanced-ripe-a… This is part of the series of interactive on-line learning sessions, that give you the opportunity to learn and interact with trainers without leaving your desk, as well as for hands-on practice, and to get your questions answered by developers. Learn how to: - Use RIPE Atlas measurements for network monitoring and troubleshooting - Use API calls for measurement creation - Integrate RIPE Atlas with existing monitoring systems Webinars start at 12:30 UTC, and take about one hour. ----------------------------- We look forward to seeing you online. Kind regards, Michela Galante and Vesna Manojlovic RIPE NCC

1 0

Travel funding for RIPE Atlas Interface Hackathon
by Michela Galante 10 Mar '16

10 Mar '16

Dear colleagues, We’re excited to announce that travel funding is now available for the RIPE Atlas Interface Hackathon! As a reminder, the 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 - and we can now help cover the cost of travel and accommodation for a number of successful applicants, thanks to the generous financial support of our sponsor, Comcast. All of the event details and application form are available online: https://atlas.ripe.net/hackathon/Interface/?pk_campaign=hackathon&pk_kwd=li… *The application deadline is 23 March* We hope to see you there! Michela and the RIPE Atlas Team

1 0

DNS64 system tag using RFC7050
by Pier Carlo Chiodi 09 Mar '16

09 Mar '16

Hello, I would like to recall this short conversation that appeared in ipv6-wg: https://www.ripe.net/ripe/mail/archives/ipv6-wg/2015-November/002747.html I was wondering if it is worth adding a new system tag to probes: something like system-dns64. >From a quick analysis that I made using RFC7050 [1] I noticed that only a handful of probes are behind a DNS64 box, but I think it would be useful to have them tagged, to avoid spending credits to detect them every time. Or perhaps the game is not worth the candle... In that case, you can find my results as of yesterday there on GitHub. Bests, 1] https://gist.github.com/pierky/e5ec5c8f8f926bff3ef3#file-ripe-atlas-rfc7050… -- Pier Carlo Chiodi

1 0

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

Small downtime expected
by Robert Kisteleki 02 Mar '16

02 Mar '16

Dear All, Due to operational reasons we will have a short downtime of the main RIPE Atlas website at 11:00 (CET). We expect this to last less than 15 minutes. The system will continue to collect results in the meantime, so no data loss is expected. Regards, Robert Kisteleki

1 0