- ripe-atlas - mailman.ripe.net

RIPE Atlas vs. bash/shellshock vulnerability
by Robert Kisteleki 03 Oct '14

03 Oct '14

Dear RIPE Atlas users, The RIPE NCC made a public announcement earlier about this issue (see https://www.ripe.net/internet-coordination/news/announcements/ripe-ncc-secu…) Still, since we have received some questions in email and Twitter about RIPE Atlas vs. this vulnerability so we'd like to respond to these with some more detail. The RIPE Atlas v1-v2-v3 probes are/were not affected by this issue at all since they don't run bash (or even have it installed) and also not providing any accessible services. The anchors have bash installed, but it is not used for any of the services provided. Besides, these servers have been patched right away. The infrastructure components (ie. controllers) were affected and as the RIPE NCC announcement explains, they have been patched as soon as the patch came out; basically within the day. Regards, Robert Kisteleki for the Atlas team

3 3

out of office
by jiri.prochazka＠superhosting.cz 01 Oct '14

01 Oct '14

Dear sender, I am currently out of office returning October 6th. I have limited access to my email, in urgent case you can reach me on my mobile phone + 420 777 87 37 67. Regards, -- Jiri Prochazka network administrator (AS39392) SuperNetwork s.r.o. m: +420 777 87 37 67 w: http://www.superhosting.cz e: jiri.prochazka(a)superhosting.cz

1 0

Wrong uptime information in monthly report
by Rene Bartsch 01 Oct '14

01 Oct '14

Hi, I got the following report of a drone: -------------------------------------------------------------------------------------------------------------- This is your monthly availability report for probe 3146 (T-Online Call & Surf Comfort IP Speed 50/10 MBit/s ). Calculation interval : 2014-09-01 00:00:00 - 2014-10-01 00:00:00 Total Connected Time : 15d 16:46 Total Disconnected Time : 14d 07:13 Total Availability : 52.33% +---------------------+---------------------+------------+--------------+ | Connected (UTC) | Disconnected (UTC) | Connected | Disconnected | |---------------------+---------------------+------------+--------------+ | 2014-08-14 11:37:26 | 2014-09-02 02:22:27 | 1d 02:22 | 0d 00:00 | | 2014-09-02 02:36:21 | 2014-09-04 23:40:28 | 2d 21:04 | 0d 00:13 | | 2014-09-05 00:03:58 | 2014-09-16 17:23:55 | 11d 17:19 | 0d 00:23 | +---------------------+---------------------+------------+--------------+ ---------------------------------------------------------------------------------------------------------------- https://atlas.ripe.net/probes/3146/#!tab-network shows an uptime of 99.83%. Please fix this! -- Best regards, Renne

2 1

Fwd: Final Call For Presentations RIPE 69, deadline 1 October 2014
by Vesna Manojlovic 25 Sep '14

25 Sep '14

Dear colleagues, RIPE69 is approaching. If you would like to present to the whole plenary on RIPE Atlas, the deadline is soon. If you prefer to talk on MAT-WG, please approach the chairs directly: mat-wg-chairs(a)ripe.net Regards, Vesna -------- Original Message -------- Date: Wed, 24 Sep 2014 23:36:36 +0200 From: Benno Overeinder <benno(a)NLnetLabs.nl> Dear colleagues, Following the past submission deadline, there is a Draft RIPE Plenary programme published at: https://ripe69.ripe.net/programme/meeting-plan/plenary/ There are still slots remaining for the final RIPE 69 programme and RIPE Programme Committee will accept new proposals until 1 October 2014. This is a last call deadline if you wish to submit a proposal. Kind regards, Benno Overeinder for RIPE programme committee On 27/08/14 13:33, Benno Overeinder wrote: > Dear colleagues, > > Please find the CFP for RIPE 69 in London below. > > The deadline for submissions is 31 August 2014. > > Please also note that speakers do not receive any extra reduction or > funding towards the meeting fee at the RIPE Meetings. > > Kind regards, > > RIPE PC > http://www.ripe.net/ripe/meetings/ripe-meetings/pc > > > --------------------- > > Call for Presentations > > A RIPE Meeting is an open event where Internet Service Providers, > network operators and other interested parties get together. Although > the meeting is mostly technical, it is also a chance for people to meet > and network with others in their field. > > RIPE 69 will take place from 3-7 November 2014 in London, UK. > > The RIPE Programme Committee (PC) is now seeking content proposals from > the RIPE community for the plenary session presentations, BoFs (Birds of > a Feather sessions), panels, workshops, tutorials and lightning talks at > RIPE 69. The PC is looking for presentations covering topics of network > engineering and operations, including but not limited to: > > - IPv6 deployment > - Managing IPv4 scarcity in operations > - Commercial transactions of IPv4 addresses > - Data centre technologies > - Network and DNS operations > - Internet governance and regulatory practices > - Network and routing security > - Content delivery > - Internet peering and mobile data exchange > > Submissions > > RIPE Meeting attendees are quite sensitive to keeping presentations > non-commercial, and product marketing talks are strongly discouraged. > Repeated audience feedback shows that the most successful talks focus on > operational experience, research results, or case studies. For example, > presenters wishing to describe a commercial solution should focus on > the underlying technology and not attempt a product demonstration. > > The RIPE PC accepts proposals for different presentation formats, > including plenary session presentations, tutorials, workshops, BoFs > (Birds of a Feather sessions) and lightning talks. See the full > descriptions of these formats at > https://ripe69.ripe.net/submit-topic/presentation-formats/ > > Presenters who are proposing a panel or BoF are encouraged to include > speakers from several (perhaps even competing) companies and/or a > neutral facilitator. > > In addition to presentations selected in advance for the plenary, the > RIPE PC also offers several time slots for "lightning talks", which are > selected immediately before or during the conference. > > The following general requirements apply: > > - Proposals for plenary session presentations, BoFs, panels, workshops > and tutorials must be submitted for full consideration no later than > 31 August 2014, using the meeting submission system at > https://ripe69.ripe.net/submit-topic/guidelines/. Proposals > submitted after this date will be considered on a space-available > basis. > > - Lightning talks should also be submitted using the meeting submission > system (https://ripe69.ripe.net/submit-topic/submission-form/) and > can be submitted just days before the RIPE Meeting starts or even > during the meeting week. The allocation of lightning talk slots will > be announced in short notice – in some cases on the same day but > often one day prior to the relevant session. > > - Presenters should indicate how much time they will require. See more > information on time slot allocations per presentation format at > https://ripe69.ripe.net/submit-topic/presentation-formats/. > > - Proposals for talks will only be considered by the PC if they contain > at least draft presentation slides (slides may be updated later on). > For panels, proposals must contain a clear description, as well as > the names of invited panellists, presenters and moderators. > > - Due to potential technical issues, it is expected that most, if not > all, presenters/panellists will be physically present at the RIPE > Meeting. > > If you have any questions or requests concerning content submissions, > please email pc [at] ripe [dot] net. > > --------------------- > > -- Benno J. Overeinder NLnet Labs http://www.nlnetlabs.nl/

1 0

UDM limit?
by Paul Vlaar 18 Sep '14

18 Sep '14

Hi, I'm trying to add a UDM for one of our nameservers, however it appears others are already doing "too many measurements" for this server, as this is the message I get when I try to add my UDM: "10 UDMs are already measuring 199.19.54.1/2001:500:c::1. Cannot add 2 more" AFAIK I have no UDMs running for this server, so the mentioned UDMs are beyond my control to retract. Is it possible to find out who is running these UDMs so I can ask them to stop, or alter them in such a way that they match what I need in this UDM? It seems a bit odd to me that I can't do custom measurements on our server because others are already doing some. ~paul -- Paul Vlaar DNS Infrastructure Group Afilias e-mail: pvlaar(a)afilias.info phone: +1-416-673-4078 mobile DE: +49-1578-5742-695 mobile NL: +31-6-506-306-35 mobile USA: +1-602-410-4148

4 6

XS4ALL (NL) has joined RIPE Atlas anchors
by Michela Galante 16 Sep '14

16 Sep '14

Dear RIPE Atlas users, We're happy to announce that another RIPE Atlas anchor has joined the network and is now available as a target for probe hosts conducting their own user-defined measurements. The new anchor is called nl-ams-as3265 and it is hosted by XS4ALL in Amsterdam, Nederland. Anchoring measurements (ping, ping6, traceroute and traceroute6) are scheduled towards this anchor from all the other anchors as well as several hundred probes, providing a continual overview of regional reachability. Results of these measurements are available as raw data in JSON format, and visualised on the map and "seismograph" with many configurable features. You can access the anchoring measurements for all anchors at: https://atlas.ripe.net/anchors/list/ Learn more about RIPE Atlas anchors at: https://atlas.ripe.net/about/anchors/ Thank you for participating in RIPE Atlas! Kind regards, Measurements Community Building Team RIPE NCC mcb(a)ripe.net

1 0

Seeking community feedback on draft RIPE Atlas Service Terms and Conditions
by Vesna Manojlovic 15 Sep '14

15 Sep '14

Dear colleagues, We have published a draft proposal for RIPE Atlas Service Terms and Conditions and are asking for community feedback on this, along with our proposed implementation plan. Please find more information on the MAT Working Group Mailing List, where we kindly ask you to direct any feedback you may have: https://www.ripe.net/ripe/mail/archives/mat-wg/2014-September/000489.html Regards, Vesna Manojlovic Senior Community Builder Measurements Community Building RIPE NCC

1 0

New on RIPE Labs: RIPE Atlas Measurements with Tagged Probes coming soon
by Mirjam Kuehne 15 Sep '14

15 Sep '14

Dear colleagues, Please find a new article on RIPE Labs: RIPE Atlas: Measurements with Tagged Probes Coming Soon https://labs.ripe.net/Members/suzanne_taylor_muzzin/ripe-atlas-measurements… If you have any comments or questions, please let us know. Kind regards, Mirjam Kuehne RIPE NCC

3 2

SCT Schiele (DE) has joined RIPE Atlas anchors
by Michela Galante 15 Sep '14

15 Sep '14

Dear RIPE Atlas users, We're happy to announce that another RIPE Atlas anchor has joined the network and is now available as a target for probe hosts conducting their own user-defined measurements. The new anchor is called de-ett-as202040 and it is hosted by SCT Schiele GmbH in Ettlingen, Germany. Anchoring measurements (ping, ping6, traceroute and traceroute6) are scheduled towards this anchor from all the other anchors as well as several hundred probes, providing a continual overview of regional reachability. Results of these measurements are available as raw data in JSON format, and visualised on the map and "seismograph" with many configurable features. You can access the anchoring measurements for all anchors at: https://atlas.ripe.net/anchors/list/ Learn more about RIPE Atlas anchors at: https://atlas.ripe.net/about/anchors/ Thank you for participating in RIPE Atlas! Kind regards, Measurements Community Building Team RIPE NCC mcb(a)ripe.net

1 0

'limit' filed in the probe API metadata
by Eravuchira, Steffie Jacob 12 Sep '14

12 Sep '14

Hello, In the REST API for RIPE Atlas probes [1], there is a metadata "limit" to set the number of items displayed in the API [2]. Previously I have used the "limit" field to get the details of all the registered probes (by specifying limit as the value in the field "total_count" in metadata) at once using this API. Now the API works well with values of "limit" up to 100. But for any value greater than 100, the limit is automatically set to 100. Could anyone help me understand why this could happen and how I can access the details of all the RIPE Atlas registered probes? [1] https://atlas.ripe.net/api/v1/probe [2] https://atlas.ripe.net/api/v1/probe/?limit=n Thank you in advance for the help. Regards, Steffie _________________________________________________________ Steffie Jacob Eravuchira Research I, Room 91 Computer Networks and Distributed Systems (CNDS) Lab School of Engineering and Sciences Jacobs University Bremen, Germany

2 1