- ripe-atlas - mailman.ripe.net

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

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

Detecting additional information from the probes
by Christoph Rauterberg 15 Feb '16

15 Feb '16

Ahoi everyone, I am currently trying to asses the behaviour of DNS queries between clients and authentication servers - and I would love to trace some DNS pakets between the probes and my server. I was wondering, if there is some way to get the information about the Authentication Bit of DNSSEC specified in the DNS query headers. A.f.a.i.k., the probes do something similiar/do a /dig/ lookup. /dig/ does provide information about the DNSSEC-section - and furthermore it has a very handy /+trace/ option. Can anyone maybe tell me, if there are possibilities to access the AUTH bith or even something like a trace function via the probes? Or should I open a feature request for that? Help much appreciated! :-) Best regards, Chris

2 3

can help me increase speed
by mostafa shahdadi 13 Feb '16

13 Feb '16

% This is the RIPE Database query service. % The objects are in RPSL format. % % The RIPE Database is subject to Terms and Conditions. % See http://www.ripe.net/db/support/db-terms-conditions.pdf % Note: this output has been filtered. % To receive output for a database update, use the "-B" flag. % Information related to '2.189.88.0 - 2.189.95.255' % Abuse contact for '2.189.88.0 - 2.189.95.255' is 'R.javidi(a)tci.ir' inetnum: 2.189.88.0 - 2.189.95.255 netname: DABCO descr: Dadeh Pardazan Avaye Bandar Company country: IR admin-c: PA8248-RIPE tech-c: PA8248-RIPE status: ASSIGNED PA mnt-by: AS12880-MNT created: 2015-05-25T06:22:46Z last-modified: 2015-05-25T06:31:59Z source: RIPE # Filtered person: POURIYA ARGHASH address: No 2,first Floor,Daryanavard Building,Delgosha Conjunction, address: Emam Khomeyni Street,Bandar Abbas,Hormozgan,Iran phone: +98 761 222 54 90 fax-no: +98 761 222 54 90 nic-hdl: PA8248-RIPE mnt-by: AS12880-MNT created: 2015-05-25T06:31:59Z last-modified: 2015-05-25T06:31:59Z source: RIPE # Filtered % Information related to '2.189.0.0/16AS12880' route: 2.189.0.0/16 descr: Information Technology Company (ITC) origin: AS12880 mnt-by: AS12880-MNT mnt-routes: mohsenrahimimaintainer created: 2011-07-13T14:32:16Z last-modified: 2015-03-04T10:05:36Z source: RIPE # Filtered % This query was served by the RIPE Database Query Service version 1.85.1 (DB-1) Sent from my iPad

2 1

Triggering traces from probes in specific cities
by Anurag Bhatia 10 Feb '16

10 Feb '16

Hello everyone, I was looking at possible command line tool to trigger traces from Atlas from given city or that area. The closest I can see is RIPE Atlas Tools - https://github.com/RIPE-NCC/ripe-atlas-tools but these let to only put source country or region. 1. Is anyone aware of how one can trigger traces via CLI from specific cities? *(I would love to do trace from a nearby city if specific city does not have Atlas coverage)* 2. In the Ripe Atlas Tools I see in documentation it refers to an argument "[--paris paris]". Is anyone aware of what does it mean? It seems to be asking for an integer value. Thanks in advance! -- Anurag Bhatia anuragbhatia.com

2 2