- ripe-atlas - mailman.ripe.net

Leftover budget? Consider a RIPE Atlas anchor
by Vesna Manojlovic 27 Nov '15

27 Nov '15

Dear all, The end of the year is coming closer, and you might be wondering, “What is the best way to spend some of the money still left in my budget, while at the same time contributing to the good of the Internet?” Why not consider hosting a RIPE Atlas anchor?! Investing in an anchor means you will: - Gain access to a wealth of measurement data (IPv4/IPv6 pings, trace routes) targeting your anchor from all the other anchors and hundreds of probes throughout the RIPE Atlas network, without spending credits - Earn 10 times more credits compared to hosing a regular probe that you can spend on your own customised measurements - HTTP measurements towards your anchor [1] - Have your logo included on the RIPE Atlas website [2] - Join a growing community that is providing great benefit to the Internet: there are currently 159 RIPE Atlas anchors around the world You can learn more about hosting an anchor here: https://atlas.ripe.net/get-involved/become-an-anchor-host/ Thanks, and happy holiday season! Vesna [1] https://labs.ripe.net/Members/kistel/ripe-atlas-update-http-measurements-cl… [2] https://atlas.ripe.net/get-involved/community/#!anchor-sponsors

1 0

Invitation: RIPE NCC Member Lunches in London & Manchester, mid-December 2015
by Vesna Manojlovic 26 Nov '15

26 Nov '15

Dear colleagues, We warmly invite you to join us for a RIPE NCC Member Lunches: - in London on Wednesday, 9 December. - in Manchester on Thursday, 10 December The lunch gives members an open-discussion format to exchange ideas and information among each other as well as with RIPE NCC staff. The goal of these lunches is to offer you an opportunity to meet up with our staff and discuss how we can better engage with the local technical community. Members may also use this opportunity to voice concerns as well as resolve any issues with resource requests or open tickets. I will be there to talk about RIPE Atlas and other measurements & statistics related topics; my colleagues will be there to answer any other questions. This is a free event, with capacity for around 30 people, so we would appreciate an indication of whether you or any of your colleagues wish to attend (up to two attendees from a single LIR). Please confirm your attendance by filling out the registration form below. All who register will be sent a further information sheet prior to the meeting. You can learn more about the services RIPE NCC provides for our members and the RIPE community at: http://www.ripe.net/lir-services/ncc/list-of-ripe-ncc-services We look forward to meeting you in December! Kind regards, Vesna Manojlovic Community Builder & Fergal Cunningham Membership Communications Officer RIPE NCC Details & registration: ======================= London ====== The lunch will be held on Wednesday, 9 December from 13:00-15:00 (arrival from 12:30) at: De Hems Dutch Cafe Bar Dutch-themed, traditional 19th-century pub serving Dutch and Belgian beers, British menu and snacks. Address: 11 Macclesfield St, London W1D 5BW Register: https://portal.ripe.net/meeting-pub/registration?meetingId=b1400c45-7b87-49… Manchester ========== The lunch will be held on Thursday, 10 December from 13:00-15:00 (arrival from 12:30) at: Address: The Lowry Hotel 50 Dearmans Pl, Chapel Wharf, Manchester M3 5LH, United Kingdom https://www.thelowryhotel.com/restaurants-and-bars/river-bar-and-grill Register: https://portal.ripe.net/meeting-pub/registration?meetingId=2d9ce8d0-46e7-43…

1 0

[Request] System tags for DNS resolution
by Stephane Bortzmeyer 18 Nov '15

18 Nov '15

[Is there a better way to record enhancement requests for Atlas? Atlas has no public issue tracker, if I'm correct?] It would be cool to have system (automatic) tags for DNS resolution because some probes are using broken DNS resolvers. For instance, system-dns-works (modeled on IPv6's system tag) would be fine. Or may be system-dns-resolver-works (longer but more accurate). For instance, probes 16659, 17072, 17620, 17854 use a resolver which yields a REFUSED for any request and probe 19948, 20065 one with systematic SERVFAIL. [Is the maintainer of the probe automatically notified when there is such an issue?]

4 6

Seven new RIPE Atlas anchors have joined the community
by Michela Galante 18 Nov '15

18 Nov '15

Dear RIPE Atlas users, Seven new RIPE Atlas anchors have been activated bringing the total number to 157. - Three anchors hosted by Leaseweb Network: us-mnz-as30633 in Manassas, Virginia, us-sfo-as7203 in San Francisco, California, and sg-sin-as59253 in Singapore. - jp-tyo-as13901, hosted by Afilias in Tokyo, Japan. - de-gaa-as56357, hosted by Technische Universität München in Garching, Germany. - cl-scl-as27678, hosted by NIC Chile in Santiago, Chile and sponsored by LACNIC. - pe-lim-as27843, hosted by Optical Technologies in Lima, Peru. 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

Probe with no firmware
by Anne Inapat 18 Nov '15

18 Nov '15

I registered my probe almost 2 days ago. when I check on the probe on your site, it is indicated no firmware. I am also unable to get an IP through DHCP. Kindly help.

1 0

Any way to select the probes from upstream AS (not origin AS)?
by Stephane Bortzmeyer 16 Nov '15

16 Nov '15

Is there an easy way to select probes, not on the origin AS, but on an AS upstream? Example: probe 23865, IP prefix announced by AS 56339 which currently has only one provider, AS 16080. Currently, Atlas tells me there are no probes in AS 16080...

4 4

Architecture and firmware version filter in probe selection
by Yang Yu 13 Nov '15

13 Nov '15

It would be nice to be able to set architecture and firmware version criteria when selecting probes, making the results more consistent and avoid unnecessary measurements in certain cases. Yang

2 1

Feature request for Traceroute in RIPE Atlas
by Yue LI 13 Nov '15

13 Nov '15

Dear all, So far, the Atlas traceroute is such that if there are 5 consecutive hops with only timeouts (denoted by a star "*"), traceroute will directly try hop 255 and then stop the measurement, which means that the number of total hops can not be obtained. An example can be found: https://atlas.ripe.net/measurements/2841001/#!probes (the probe #22341) Unfortunately, the number of hops is so important to be used as a metric to evaluate the performance of a new protocol. Thus, I propose to add a configuration option for the number of hops after which traceroute decides to call it quits. I wonder whether there are somebody else are also interested in this new feature please? Best regards, Yue -- Yue LI PhD student, Telecom ParisTech Tel: +33 (0)661091840 E-mail: yueli.cnfr(a)gmail.com

1 0

New on RIPE Labs: RIPE Atlas WiFi Measurements
by Robert Kisteleki 13 Nov '15

13 Nov '15

Dear colleagues, We're thinking about implementing WiFi measurements in RIPE Atlas, and we want to know what you think. There are several different ways we could do this - find out more on RIPE Labs and then take our poll to make your voice heard! https://labs.ripe.net/Members/suzanne_taylor_muzzin/ripe-atlas-wifi-measure… Kind regards, Mirjam Kuehne & Robert Kisteleki RIPE NCC

2 1

edst 193.0.0.228 in traceroute results
by Yang Yu 13 Nov '15

13 Nov '15

Hello, In https://atlas.ripe.net/measurements/2928258, I did a UDP traceroute. "edst":"193.0.0.228" from first hop and second hop somehow showed up in the results after the last hop that responded to traceroute, which should have been a reply to buil-in measurement to tt01.ripe.net. And under maps tab the result is presented with the first 2 hops showing up after several non-responding hops. Is this a bug? I actually see it happening quite often in atlas traceroute results with firmware > 4680. Another example is https://atlas.ripe.net/measurements/2928262 >>> https://atlas.ripe.net/docs/bugs/ 2015-03-04 Before firmware 4680, traceroute could experience interference from other measurements. In general, periodic traceroutes did not interfere with other periodic traceroutes, but could experience interference from one-off traceroutes. Typically, this interference will show up in the 'edst' field. This problem was fixed in 4680. Thanks. Yang

1 0