July 2013 - mat-wg - mailman.ripe.net

RIPE Atlas maintenance on Tuesday, 6 August
by Robert Kisteleki 31 Jul '13

31 Jul '13

Dear RIPE Atlas users, We'd like to let you know that we plan to perform scheduled maintenance on the RIPE Atlas central infrastructure on Tuesday, 6 August, for a couple of hours during the day. In this period, main features including the RIPE Atlas user interface (atlas.ripe.net), data downloads and measurement scheduling functions will be unavailable. Probes will continue to work and all results will still be collected or buffered; however, during the maintenance period you will be unable to log in to the website, manage your probes/measurements, or get to result data/visualisations. We apologise for any inconvenience this may cause. Regards, Robert Kisteleki

1 0

Re: [mat-wg] [atlas] Spoofing the source IP address from a probe?
by Andrei Robachevsky 30 Jul '13

30 Jul '13

Alex Saroyan wrote on 7/18/13 8:53 AM: > Hi, > > I think some hosts would like theirs probes to be used for "source IP > spoofing" check, and only such probes could be used for this particular > type of check. > If RIPE Atlas team implement such features then probably many hosts will > "enable" "Source IP spoofing check ability" on theirs probes and that > can serve for community at the end. I support this point of view. I think controlled (anti-)spoofing measurements performed by the RIPE NCC with the consent of participating probes would be a good service to the community. I understand that a certain percentage of probes is sitting behind NAT where spoofing won't work in most cases, but there is hopefully a significant number of probes that are connected directly. Regarding the problem itself we are tackling here, we published a follow up to the panel we held at RIPE66: http://www.internetsociety.org/doc/anti-spoofing-continuing-dialogue. Hope this helps raising awareness of the issue further. > Of course overall mechanism should be in a way not make anyone to > suspect that probe can do spoofing by default or probe can do any > harmful thing. > Agree, Andrei > Alex Saroyan > > On 06/12/2013 10:37 PM, Daniel Karrenberg wrote: >> On 12.06.2013, at 17:44 , Joe Provo <jzp-ripe(a)rsuc.gweep.net> wrote: >> >>> I would encourage those in the community who wish to be >>> performing individual spoof testing (or instruct others how >>> to do so) to use the easy-peasey pointy-clicky CAIDA/CSAIL >>> tool: http://spoofer.cmand.org/ >>> (also spoofer.csail.mit.edu, spooftest.net, etc etc) >> Seconded. Using this something like this is a conscious decision of >> the user. I have personally run Robert Beverley's probes regularly for >> many years and I am proud to say that both my broadband providers have >> never allowed source address spoofing. This involves a conscious >> decision on my part taking into account local network etiquette, my >> relation to my providers and the local legal situation. It is very >> very different from the RIPE community deciding to use RIPE Atlas to >> do this from my network. >> >> Daniel > >

2 2

Re: [mat-wg] [atlas] Spoofing the source IP address from a probe?
by Alex Saroyan 30 Jul '13

30 Jul '13

Hi, Probably we don't need to spoof all address space, instead only if spoofing enabled just spoof to some predefined address range. Regards. /Alex Sanjeev Gupta <ghane0(a)gmail.com> wrote: >On Tue, Jul 30, 2013 at 11:22 AM, Randy Bush <randy(a)psg.com> wrote: > >> I support this point of view. I think controlled (anti-)spoofing >> measurements performed by the RIPE NCC with the consent of >> participating probes would be a good service to the community. > >perhaps the probe owners are not the only parties with skin in the game >and whose consent would be relevant? > > >Exactly. I host probes, and since you are spoofing others, we need to ask them. > >How you do this is left as an exercise to the reader. > >-- >Sanjeev Gupta >+65 98551208 http://www.linkedin.com/in/ghane > > >

1 0

Atlas UDMs and Probe-Assignments
by Gert Doering 26 Jul '13

26 Jul '13

Hi, I'm wondering about something, maybe one of you can enlighten me here. I have set up a few UDMs (... to eventually get out of Atlas what we had with TTM). A small one with only 10 probes is now showing that actually only 7 probes return data - two more have returned data at some point in the past - "Jul 06, 06:11" in one case - while the 10th assigned problem seems to have never sent anything. (This is UDM 1002000, the "dead" probe is #2760 in AS 3292). The question coming from this is: how do probes get assigned to UDMs, and will dead probes get replaced eventually? Or is the assignment done statically at the beginning of the UDM? The reason why this is relevant: if I am going to set up UDMs to replace what TTM does, the idea is to have a reasonable high number of probes, say "50" or "100", and define our Internet reliability as "more than 2/3rd of the UDM probes have been answered without loss", or something like that - taking into account that somewhere on the Internet, things will always be broken, but that's not our responsibility. This falls apart of probes deteriorate after a given time, and a given UDM measurement will use "less and less probes" (so in the extreme, of the 50 initial probes, 30 might be "dead probe" and thus the result is always "0% reliability, more than 50% of the probes can not reach us"), instead of the system keeping the requested number of probes by replacing dead ones... Gert Doering -- NetMaster -- have you enabled IPv6 on something today...? SpaceNet AG Vorstand: Sebastian v. Bomhard Joseph-Dollinger-Bogen 14 Aufsichtsratsvors.: A. Grundner-Culemann D-80807 Muenchen HRB: 136055 (AG Muenchen) Tel: +49 (89) 32356-444 USt-IdNr.: DE813185279

2 4

Atlas UDM and API keys?
by Gert Doering 25 Jul '13

25 Jul '13

Hi, maybe it's too hot today, maybe I'm a bit slow, but just how do I combine the Atlas UDM download links and the API KEY to form a "download will just work" URL? The download URL I want to use is https://atlas.ripe.net/api/v1/measurement/1002000/result/?start=1373972036&… so where does the API key go? Adding "?key=<key data>" or "?apikey=..." or "just the key with no tag" didn't work... Gert Doering -- NetMaster -- have you enabled IPv6 on something today...? SpaceNet AG Vorstand: Sebastian v. Bomhard Joseph-Dollinger-Bogen 14 Aufsichtsratsvors.: A. Grundner-Culemann D-80807 Muenchen HRB: 136055 (AG Muenchen) Tel: +49 (89) 32356-444 USt-IdNr.: DE813185279

1 1

New on RIPE Labs: In-widget Comparison and Monitoring in RIPEstat
by Mirjam Kuehne 24 Jul '13

24 Jul '13

Dear colleagues, You can now monitor network events in real time in two RIPEstat widgets: Country Routing Statistics and BGP Update Activity. And we would like to hear from you for which widgets we should provide this functionality next. Please find more details on RIPE Labs: https://labs.ripe.net/Members/suzanne_taylor_muzzin/new-in-ripestat-in-widg… Kind regards, Mirjam Kuehne RIPE NCC

1 0

Call for Papers: RIPE 67, 14-18 October 2013 in Athens, Greece
by Benno Overeinder 23 Jul '13

23 Jul '13

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 67 will take place from 14-18 October 2013 in Athens, Greece. 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 67. 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://ripe67.ripe.net/programme/i-want-to-present/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 4 August 2013, using the meeting submission system (https://ripe67.ripe.net/submit-topic/). 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://ripe67.ripe.net/submit-topic/) 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 (https://ripe67.ripe.net/programme/i-want-to-present/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 panelists, presenters and moderators. - Due to potential technical issues, it is expected that most, if not all, presenters/panelists 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

PORTOLAN: A Mobile Crowdsourcing Measurement System
by Luciano Lenzini 08 Jul '13

08 Jul '13

Dear All, The University of Pisa and IIT, an Institute of the Italian National Research Council, have developed a mobile crowdsourcing-based system, named PORTOLAN which uses smartphones as mobile monitors probing the Internet and reporting results to a central server located in Pisa. The aim of PORTOLAN is to enhance the current topology of the Internet at the Autonomous System level of abstraction - all with the contribution of volunteers. The PORTOLAN component that runs on smartphones is now available as an app for the Android platform. It can be downloaded by users from Google play ( <https://play.google.com/store/apps/details?id=it.unipi.iet.portolan.tracero ute> https://play.google.com/store/apps/details?id=it.unipi.iet.portolan.tracerou te). PORTOLAN works in the background, it is designed not to interfere in any way with users' activities and does not affect the smartphone's overall performance. In order to motivate users to contribute to the PORTOLAN project, we have added several services, which include diagnostic network tools (such as Ping, Paris Traceroute with Multipath Detection Algorithm, Maximum Throughput achievable along a path, etc.) and coverage measurement tools. All the tools are totally under the user's control. Data collected by these tools are stored in our servers, in a completely anonymous way. For details see <http://portolan.iet.unipi.it/> http://portolan.iet.unipi.it/. The success of our experiment depends upon the number of users who join the experiment. But to get people to download the app, we really need to raise as much awareness as possible regarding the PORTOLAN itself. So I would like to ask you if it would be possible for you to forward this message to your colleagues, students and anyone else who you think might be interested. Many thanks in advance for your cooperation. All the best, Luciano TECHNICAL NOTE: In PORTOLAN, each smartphone issues at max 200 traceroutes per day, which means a peak traffic rate never higher than 1 KB/s and an average traffic rate never higher than 2 MB/day. The impact of these activities on the battery consumption is negligible. Signal coverage measurements are completely costless in terms of energy or bandwidth, as the PORTOLAN app passively collects signal strength samples using GPS positions generated by other apps. You have to activate the GPS yourself if you want a coverage map along your route. Given that your route could be up to 50 km or more, then you will obviously use up quite a bit of your battery power. So if you are travelling, then connect your smartphone to a powersource in your car or in the train. In any case, if the battery level goes under 40%, PORTOLAN is automatically suspended. -------------------------------------------------------------- Prof. Luciano Lenzini Department of Information Engineering University of Pisa, Italy e-mail: l.lenzini(a)iet.unipi.it http://www.iet.unipi.it/~lenzini

1 0

New on RIPE Labs: Are All Addresses Equal? (by Stephane Bortzmeyer)
by Mirjam Kuehne 03 Jul '13

03 Jul '13

Dear colleagues, Stephane Bortzmeyer describes another use case for RIPE Atlas: Are IPv4 addresses in which the last byte is zero treated differently than other IPv4 addresses? See his study on RIPE Labs: https://labs.ripe.net/Members/stephane_bortzmeyer/all-ip-addresses-are-equa… Kind regards, Mirjam Kuehne RIPE NCC

1 0

RIPE Atlas Mid-summer community update
by Vesna Manojlovic 01 Jul '13

01 Jul '13

Der colleagues, RIPE Atlas community has been very active recently. I summerized it (ha! pun intended) in the RIPE Labs article, highlighting new community related features for RIPE Atlas anchor hosts, sponsors and "ambassadors". And the article has lots of pretty pictures! Share and enjoy! Warm regards, Vesna https://labs.ripe.net/Members/becha/ripe-atlas-midsummer-2013-community-upd…

1 0