From mir at ripe.net Tue Dec 6 12:27:46 2016 From: mir at ripe.net (Mirjam Kuehne) Date: Tue, 6 Dec 2016 12:27:46 +0100 Subject: [atlas] New on RIPE Labs: Countering RIPE Atlas Hardware Issues with Better Firmware Message-ID: <10e3a1e5-788d-34de-0f06-b68cb7b6c446@ripe.net> Dear colleagues, We're working on installing better firmware in order to counter hardware issues with RIPE Atlas. Please find more information on RIPE Labs: https://labs.ripe.net/Members/kistel/ripe-atlas-countering-hardware-issues-with-better-firmware Kind regards, Mirjam Kuehne RIPE NCC From robert at ripe.net Wed Dec 7 10:46:47 2016 From: robert at ripe.net (Robert Kisteleki) Date: Wed, 7 Dec 2016 10:46:47 +0100 Subject: [atlas] RIPE Atlas and nagios status-checks In-Reply-To: References: Message-ID: <28939190-227f-94f7-8cbd-29cc33d23610@ripe.net> Hello, Update: about half an hour ago we re-enabled this configuration. If you suddenly get 403 errors from the status check service using nagios/icinga, then you'll need to change your configuration. Regards, Robert Kisteleki On 2016-11-18 13:39, Robert Kisteleki wrote: > Dear All, > > The following message may be of interest to you if you're using Nagios (or > variations like icinga) to query RIPE Atlas for status-checks. > > Yesterday morning our operations team made a change to the service > configuration such that atlas.ripe.net only answers queries if they have > proper Host: headers set. This is arguably a good operational practice, so > we'd like to enforce it. > > However, one of the users running said nagios checks noticed that this > causes 403 answers instead of the expected behaviour. We concluded that this > is because the check_http plugin doesn't always set the Host: header. > According to our statistics in total 12 users are affected, and since we > could not foresee this problem, we temporarily reverted our configuration to > the old settings. > > The fix on the client side is easy: one needs to add "-H atlas.ripe.net" > parameter (or a similar change depending on forks and versions) to the > checks. We'd like to ask our user to apply this change in the next two weeks > in order to send well-formatted requests to our service. > > Thank you, > Robert Kisteleki > RIPE NCC From marty at martystrong.co.uk Wed Dec 7 18:23:34 2016 From: marty at martystrong.co.uk (Marty Strong) Date: Wed, 7 Dec 2016 17:23:34 +0000 Subject: [atlas] Reporting incorrect locations Message-ID: Hi RIPE Atlas folks, Is there somewhere we can go to report a suspected incorrect location of an Atlas probe? This probe: https://atlas.ripe.net/probes/16578/ Is marked as in China, but is clearly in Australia. I couldn?t see anywhere I should report this. Marty -------------- next part -------------- An HTML attachment was scrubbed... URL: From mostafa.shahdadi at icloud.com Wed Dec 7 19:55:40 2016 From: mostafa.shahdadi at icloud.com (mostafa shahdadi) Date: Wed, 07 Dec 2016 22:25:40 +0330 Subject: [atlas] ipad air 2 Message-ID: <815289DD-C364-43BF-8780-CF79C66B1B41@icloud.com> Sent from my iPad From mostafa.shahdadi at icloud.com Wed Dec 7 19:59:09 2016 From: mostafa.shahdadi at icloud.com (mostafa shahdadi) Date: Wed, 07 Dec 2016 22:29:09 +0330 Subject: [atlas] ipad air 2 Message-ID: <9FB332BD-578A-4073-8EC6-C91B84B8478C@icloud.com> Sent from my iPad From robert at ripe.net Thu Dec 8 10:41:03 2016 From: robert at ripe.net (Robert Kisteleki) Date: Thu, 8 Dec 2016 10:41:03 +0100 Subject: [atlas] Reporting incorrect locations In-Reply-To: References: Message-ID: <3f005baf-6703-0b9e-56e6-1da03cfa014d@ripe.net> On 2016-12-07 18:23, Marty Strong wrote: > Hi RIPE Atlas folks, > > > Is there somewhere we can go to report a suspected incorrect location of an > Atlas probe? > > This probe: https://atlas.ripe.net/probes/16578/ > > Is marked as in China, but is clearly in Australia. > > I couldn?t see anywhere I should report this. > > > Marty Hi, Thanks for reporting! I reached out to the probe host who was very responsive and updated the location. We plan to introduce a more pro-active approach when the probe seems to have changed AS: in these cases there's a good change the location of the probe changed as well. Regards, Robert From jacques at lavignotte.org Thu Dec 8 18:26:32 2016 From: jacques at lavignotte.org (Jacques Lav!gnotte.) Date: Thu, 8 Dec 2016 18:26:32 +0100 Subject: [atlas] Probe 16917 started over Message-ID: after changing the usb memory stick. https://atlas.ripe.net/probes/16917/#!tab-general Regards, Jacques -- GnuPg : C8F5B1E3 WeUsePGP Because privacy matters http://weusepgp.info/ From BECHA at ripe.net Fri Dec 9 14:22:41 2016 From: BECHA at ripe.net (Vesna Manojlovic) Date: Fri, 9 Dec 2016 14:22:41 +0100 Subject: [atlas] Success Story: Zoom-in on Germany Message-ID: Dear community, we wrote an article as an example of how cross-pollination between two or more communities can create success. An overlap between IETF participants, RIPE Atlas users and listeners of a popular German podcast has led to growth in the deployment of RIPE Atlas probes. We are still interested in expanding this platform in areas and networks that need more coverage. For pictures & links, go here: https://labs.ripe.net/Members/becha/ripe-atlas-success-story-zoom-in-on-germany Text is bellow. Regards, Vesna In July 2016, during the IETF meeting in Berlin, the popular "rfc podcast" had a special episode aired an interview with Daniel Karrenberg talking about the RIPE NCC and RIPE Atlas. Thanks to the podcast listeners, and with the help of promotion on Twitter, the episode prompted many, many, MANY applications for new RIPE Atlas probe hosts. Because of both summer vacations and a temporary shortage of probes, there was a delay in shipping - but when the new batch of probes arrived at our office, we started shipping them to applicants, most of whom were from Germany. Currently, with regard to the number of active probes, Germany is leading with more than 1,000. This is more than the USA, which was in the lead for the previous few years. If you want to zoom in to this success-story, you can take a look at this RIPEstat widget. There you can see that, between 22 September and 7 October, the number of activated probes jumped from 999 to 1,157. Thank you to all the hosts, in Germany and elsewhere, who are helping to build RIPE Atlas - the largest active measurements platform! Actions Although we are happy that there is so much enthusiasm in Germany, we are still interested in increasing diversity of coverage. To this end, we're looking to reach out to: - Regions, countries and areas within countries with fewer probes - Networks (ASNs) with fewer probes - Deploying RIPE Atlas anchors instead If you would like to apply for your own RIPE Atlas probe, there is a special link just for the readers of this RIPE Labs article :) If you already have a probe, and want to get in touch: - Check out the Community pages - Follow us on Twitter - Be active on the mailing list From mir at ripe.net Thu Dec 22 11:19:50 2016 From: mir at ripe.net (Mirjam Kuehne) Date: Thu, 22 Dec 2016 11:19:50 +0100 Subject: [atlas] New on RIPE Labs: Four Years of RIPE Atlas Anchors In-Reply-To: References: Message-ID: <23047636-3197-1b5c-cd0f-58d221e734c1@ripe.net> Dear colleagues, Four years have passed since the RIPE NCC announced its plans to put RIPE Atlas anchors into production. Since the first anchors went online in 2013, we?ve been working hard to both maintain and expand the network. As a result, we currently have 238 anchors deployed across 66 countries! Please find more on RIPE Labs: https://labs.ripe.net/Members/alun_davies/four-years-of-ripe-atlas-anchors Kind regards, Mirjam Kuehne RIPE NCC From mostafa.shahdadi at icloud.com Thu Dec 22 13:45:08 2016 From: mostafa.shahdadi at icloud.com (mostafa shahdadi) Date: Thu, 22 Dec 2016 16:15:08 +0330 Subject: [atlas] Http Message-ID: Sent from my iPad From BECHA at ripe.net Wed Dec 28 17:11:13 2016 From: BECHA at ripe.net (Vesna Manojlovic) Date: Wed, 28 Dec 2016 17:11:13 +0100 Subject: [atlas] RIPE Atlas Probes at Hackerspaces Message-ID: <43a4ed55-d77a-9920-1f48-a8348c268af6@ripe.net> Dear all, here is an example of the possible communities that are now easier to build around RIPE Atlas probes. With the tagging of similar probes, existing communities can use additional tools for creating and analysing RIPE Atlas measurements, such as "IXP Country Jedi", to create their own interpretation of the available data. The example we used is - hackerspaces: "community-operated physical places, where people share their interest in tinkering with technology, meet and work on their projects, and learn from each other." We are hoping this is going to be an inspiration to the reader, and an invitation to play with the results and improve on the code. Longer story, with pictures, is available on RIPE Labs: https://labs.ripe.net/Members/becha/the-next-42-ripe-atlas-probes-at-hackerspaces/view Regards, Vesna