- ripe-atlas - mailman.ripe.net

Probe uptime reporting issues
by Robert Kisteleki 01 Oct '13

01 Oct '13

Dear All, On 21 September we deployed a new software version on our core infrastructure components. Unfortunately this contained a bug that we didn't catch in time, which caused "probe uptime reports" not to be propagated properly. This affected the "monthly probe uptime reports" as well as -- in some cases -- the amount of credits received for a probe. We've fixed the bug and re-sent the missing uptime entries. Please let us know (in an email to atlas(a)ripe.net, mentioning your email address and probe ID) if you received less credits than you should have, and would like to receive compensation. In order to improve our process, we're working on an internal test suite that will help us catching these kind of errors in time. We aplogise for the inconvenience this issue may have casued. Regards, Robert Kisteleki for the RIPE Atlas team

1 0

Credits transfer no longer working?
by Stephane Bortzmeyer 30 Sep '13

30 Sep '13

Did anyone notice problems with credit transfers? I run a RIPE Atlas workshop tomorrow abnd I tried to transfer credits to attendants, people with a RIPE account, both in the same LIR and outside. Nothing is credited on their side.

4 4

finding a probe
by Randy Bush 27 Sep '13

27 Sep '13

remote hands plugged an old style probe in. i see it on the ether port they claimed, its mac is 00:80:a3:91:4b:0d (my others are all 00:20, hmmm) i plug the dhcp-issued address 198.180.152.27 into the page at https://atlas.ripe.net/register/ it tells me there is no probe there how to debug? randy

1 0

REST API Problems for DNS measurements with DO and TCP
by Klaus Darilion 26 Sep '13

26 Sep '13

Hi! I managed to create DNS measurements via the REST API, but fail to set the DO and protocol:TCP option. According to the documentation (https://atlas.ripe.net/doc/measurement-creation-api/) the relevant properties are use_EDNS0 and use_tcp. So I tried it with { "definitions": [ { "is_public": true, "is_oneoff" : false, "target": "194.0.25.13", "description": "a.dns.nic.versicherung_IP4_TCP_noDO", "type": "dns", "af": 4, "interval": 300, "use_EDNS0": false, "use_TCP": true, "use_probe_resolver": false, "use_NSID": true, "query_class": "IN", "query_type": "SOA", "query_argument": "versicherung", "udp_payload_size": 1024, "protocol": "TCP", "do": true } ], } but that does not work - the generated measurements do not use TCP and DO. When I create the measurement via the web interface and review the measurement via the REST API, I see that other properties are set: "do" and "protocol". E.g: # curl https://atlas.ripe.net/api/v1/measurement/1027747/ {"all_scheduling_requests_fulfilled": true, "can_visualise": false, "creation_time": 1380018470, "description": "TEST via WEB", "do": true, "dst_addr": "194.0.25.13", "dst_asn": "1921", "dst_name": "194.0.25.13", "interval": 240, "is_oneoff": true, "is_public": true, "msm_id": 1027747, "nsid": true, "participant_count": 1, "protocol": "TCP", "query": {"class": "IN", "type": "SOA", "value": "versicherung."}, "resolve_on_probe": false, "resolved_ips": ["194.0.25.13"], "result": "/api/v1/measurement/1027747/result/", "start_time": 1380018470, "status": {"id": 7, "name": "Failed"}, "stop_time": 1380018904, "type": {"id": 6, "name": "dns"}, "udp_payload_size": 512} So I tried to create measurements with the "do" and "protocol" properties, but these properties are again ignored. If I am doing something wrong, so please give me some hints. Otherwise the API documentation is wrong and these properties can not be set via REST, only via the web interface - and should be fixed. Thanks Klaus

3 6

IPv6, RA and static IPv6 assignment
by Mike. 19 Sep '13

19 Sep '13

Are there any plans to allow the probe's listening for RA to be disabled so that I can configure a static IPv6 address, router and DNS server without RA overwriting my values?

4 4

Add E-Mail notification when a probe is back up (for more than 60 minutes)
by Roman Mamedov 19 Sep '13

19 Sep '13

Hello, Got one of these: > Your probe 73 has been disconnected since 2013-09-19 09:26:19 UTC. > > This is an automatically generated email from RIPE Atlas. It was sent to you because you asked to be notified if your probe becomes disconnected for more than 60 minutes. > > If you want to change this, or disable this notification altogether, please go to https://atlas.ripe.net/atlas/myprobes.html, click on "My Probes" and then on probe 73. In the opened tab, select "Probe's Settings" and then "Notifications" to change your settings. > > Kind regards, > > RIPE Atlas Team > What's unusual this time, is that I did not change anything in my network setup, and I can still ping the probe both on its local v4 and global v6 addresses. So one way of action would be to unplug and replug the probe in hope that it sorts out itself; 2nd course of action would be to simply wait and see if it reconnects on its own. If I choose this, I have to keep the Atlas website open in a browser tab, refreshing from time to time to see if the readings changed to "Connected". So what baffles me about this, why can't I get a simple E-Mail notification same way as "it went down", to tell me that "ok now it's back up"? -- With respect, Roman

1 0

"Spoofing" tests.
by Warren Kumari 18 Sep '13

18 Sep '13

Apologies if this has already been discussed enlist -- I took a quick look though the archives and didn't see it. I believe that the reason for not allowing things like tests that send spoofed packets is that it might violate the AUP that participants have with their ISPs / be viewed by participants ISPs as an attack. So, what about having a checkbox in the Probe Settings that says something like: "I have no AUP with my ISP or I'm fine to violate my AUP. Run intrusive or dangerous tests on this probe" ? This would create a subset of probes that could be used for more interesting tests, an d would allow for greater visibility into things. W --- It is a mistake to think you can solve any major problem just with potatoes. --Douglas Adams

11 17

RIPE Atlas anchors update
by becha 16 Sep '13

16 Sep '13

Dear RIPE Atlas users, we are happy to share with you the results of the pilot phase of RIPE Atlas anchors, and plans for the production service. Two recent RIPE Labs article give you the details: * technical results of virtualization testing: https://labs.ripe.net/Members/romeo_zwart/further-virtualisation-testing-fo… * "mesh" measurements between all anchors, moving to smaller box and different hardware platform, and making the service for all, not only members: https://labs.ripe.net/Members/becha/ripe-atlas-anchors-pilot-summary-and-ne… We are looking forward to see you at RIPE67, MAT-WG, and in the meantime, to your comments and feedback on this list. Kind regards, Vesna -- Vesna Manojlovic BECHA(a)ripe.net Senior Community Builder @Ms_Measurements for Measurements Tools RIPE NCC http://ripe.net

1 0

No IPv6 Connection on Probe
by David Churchill 13 Sep '13

13 Sep '13

I've noticed that my probe (12070) has not had any IPv6 connectivity for the last several days. I've reset the probe a couple of times and verified that my internet service still has full IPv6 connectivity (@http://test-ipv6.comcast.net/). Is there anything I can do to restore the IPv6 connectivity? Thanks, David C. Churchill 5285 Vinings Springs Trl Mableton, GA 30126 770.819.5935 d_churchill(a)comcast.net

2 1

A small matter of terminology
by Stephane Bortzmeyer 10 Sep '13

10 Sep '13

A long time ago, there was only one sort of measurement. Then, one-off measurements were created. How do we call the other category? Periodic measurements? Repeated measurements?

1 0

New On RIPE Labs: The Seismograph And Other RIPE Atlas Features
by Michela Galante 09 Sep '13

09 Sep '13

Dear colleagues, We have added a couple of new RIPE Atlas features including the Seismograph, zoomable ping graphs and others. You can find the details in an article on RIPE Labs here: https://labs.ripe.net/Members/becha/seismograph-and-other-new-ripe-atlas-fe… Kind regards Michela Galante Project Coordinator RIPE NCC

1 0

Using Atlas for commercial services
by Stephane Bortzmeyer 05 Sep '13

05 Sep '13

Hello, happy Atlasers, After reading <https://labs.ripe.net/Members/kranjbar/future-of-ripe-ncc-technical-services> (specially the part about using Atlas to monitor reachability from Nagios), the ToS <https://atlas.ripe.net/service-rules/> and checking the FAQ <https://atlas.ripe.net/about/faq/>, I still have a question: Can I use Atlas as a basis for commercial services? Today, most Atlas uses seem to be for public research, or for "selfish" measurements (checking my network). But I see nothing forbidding people to sell services (monitoring, quality assessment) to other people, based on Atlas. Is it on purpose? [Yes, I have one or two business ideas and I would like to know before I continue developing them.]

11 15

Re: [atlas] Using Atlas for commercial services
by Hook 05 Sep '13

05 Sep '13

As already said, commercial usage would also mean that you have to earn credits in some way. As far as I know, it's only possible to earn credits by - hosting probes itself - sponsoring new probes - getting a LIR In either of the first two cases, the atlas project will benefit from it. The third one is a special case and isn't worth a discussion. So I think we should allow commercial usage of the Atlas project, if commercial usage still means to support the Atlas project itself because of the need for credits! Would be a win-win situation. Michael 2013/9/5 Daniel Karrenberg <daniel.karrenberg(a)ripe.net> > > On 05.09.2013, at 11:42 , Stephane Bortzmeyer <bortzmeyer(a)nic.fr> wrote: > > > On Thu, Sep 05, 2013 at 05:22:50PM +0800, > > Sanjeev Gupta <ghane0(a)gmail.com> wrote > > a message of 107 lines which said: > > > >> Adam Smith was right, the baker and the butcher feed me by being > selfish. > > > > So, apparently, there is no consensus among the Atlas community. An > > interesting discussion to have in Athens? > > It is a discussion we should have in the mat-wg. The working groups work > on the mailing lists; physical meetings are just focal points for the work. > > Daniel > > >

1 0

Disabling one measurement on my probe...
by Warren Kumari 02 Sep '13

02 Sep '13

Hi all, Due to much stupidity my probe lives behind 2 NATs (don't ask). Anyway, one of the NATs / firewalls is suddenly throwing hissyfits and logging a bunch of messages like: [00005] 2013-08-27 17:33:29 [Root]system-critical-00435: ICMP fragment! From 78.46.37.134 to 192.168.15.207, proto 1 (zone Untrust, int ethernet3). Occurred 2 times. I can see the Measurement IDs that are causing this (1019675, 1019728), but I have two questions: 1: is there a way to disable specific measurements from a specific probe and 2: did anything change recently with the "Ping" measurement, like the packet size for example? I *did* spend some time reading the list archives and documentation, but was not able to find an answer. W P.S: And yes, I will sometime remove the NATs, but cannot until there is another ISP available -- I live in a 3rd world country where any broadened is a luxury, and multiple providers is more than one can reasonably expect… -- "When it comes to glittering objects, wizards have all the taste and self-control of a deranged magpie." -- Terry Pratchett

4 4

Data visualization not working?
by Max Grobecker 29 Aug '13

29 Aug '13

Hi, is there any known reason/issue why new created measurements don't visualize the data? I'm pretty sure I ticked the "Visualize Data" box when creating a new measurement, but when I open my new measurement, the "RRD" tab is missing and in the settings the "Visualize" box is unchecked :-( Is it just me or do other people have the same issue? Greetings, Max

2 2

Reddit?
by Daniel Quinn 29 Aug '13

29 Aug '13

Hello everyone, I'm one of the developers on the RIPE Atlas project and I'm hoping some of you can help me figure out if we should have a presence on [Reddit](http://www.reddit.com/) and if so, where. I'm a pretty active member of that community, so I was appointed to ask the lot of you if we should bother setting up a subreddit, or if we should just frequent any particular subreddit to answer questions and/or promote RIPE Atlas. So, does anyone reading this fancy the idea of better outreach on Reddit? And if so, in what way would you recommend? Feel free to post your responses to the list, or just respond to me directly. We'll let you know if we decide to branch out in this way.

3 4

Success stories to share at RIPE67?
by Vesna Manojlovic 27 Aug '13

27 Aug '13

Hi RIPE Atlas active hosts & users, I know of two RIPE Atlas related talks that are still being considered for RIPE67 -- and there might be more! Do you have a success story to share? Plenary-talks CallForPapers is extended, and then there are working-group sessions too, MAT-wg being the most typical, but in the past there were presentations on using RIPE Atlas in IPv6-WG and DNS, and Routing-WG... If you need help with preparing slides, or doing extra measurements to prove your tests - do let us know! Good luck if you decide to present, and see you at RIPE67! Regards, Vesna -------- Original Message -------- Dear Colleagues, A list of currently accepted RIPE 67 Plenary talks, BoFs, Tutorials and Workshops is now published at: https://ripe67.ripe.net/programme/meeting-plan/draft-programme/ There are still few slots remaining for a final RIPE 67 programme and RIPE Programme Committee will accept new proposals until *9 September 2013*. This is our last call for you to submit your proposals. See https://ripe67.ripe.net/programme/cfp/ or find the original CFP below. Kind regards Filiz Yilmaz for RIPE Programme Committee ------------------ 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.

1 0

Garbage Measurements
by Michael Stevens 26 Aug '13

26 Aug '13

Hello, at the moment I'm seeing a lot of measurements on my both probes, that doesn't have any live target and, sometimes, have even invalid targets like 2001:db8:0:dead:beef::1 which is part of the IPv6 for documentation purposes. I've made a screenshot here: http://i.imgur.com/PRXHsOZ.png Can someone from RIPE check this out? Not sure if there is someone abusing RIPE Atlas in a nasty way. Michael

5 5

Crediting for probe uptime
by Robert Kisteleki 23 Aug '13

23 Aug '13

Dear All, In the last two days we noticed a hickup in the crediting procedure (the one that gives credits to probe hosts and sponsors). We believe the proper fix is in place now. We just finished crediting everyone for the time period in question, which means all of the probes generated more than usual credits -- compensating for the missing ones lately, and some interest :-) We apologise for the inconvenience this may have caused. Regards, Robert Kisteleki

1 0

On RIPE Labs: Future of the RIPE NCC technical services
by Vesna Manojlovic 23 Aug '13

23 Aug '13

Dear colleagues, please take a look at the Labs article by Kaveh Ranjbar, which touches upon the future of the RIPE Atlas services: https://labs.ripe.net/Members/kranjbar/future-of-ripe-ncc-technical-services Regards, Vesna

1 0

IPv6 Report - Blank
by Tom Kacprzynski 22 Aug '13

22 Aug '13

Hello, Is anyone else having the issue of downloading IPv6 measurement reports? I ran few of them and the file is empty. I tried downloading both formats JSON and Fragment. I also tried downloading the public measurement without any luck either. Thanks -- *Tom Kacprzynski*

2 2

Geo locations confirmed
by Marco Davids (SIDN) 20 Aug '13

20 Aug '13

Hi, Are any of the geo-locations of Atlas probes confirmed, double-checked, or verified by RIPE? Or do we just have to take for granted, whatever the owner of the probe enters in the probe's settings ? Thanks, -- Marco

2 1

v3 Probe got disconnected and won't reconnect
by Axel Fischer 14 Aug '13

14 Aug '13

Hi, on 2013-08-11 at 05:15:30 UTC one of our probes (ID: 11707) got disconnected. It is connected via a switch to a router within our network. I can see the link up (it remained up all the time) but see the 3rd LED (Network Test) and 4th LED (Connecting) blinking. The MAC was visible on the switch port and router. I powercycled the probe but no change except that the MAC is no longer visible on the router. With a laptop instead of the probe it works fine. Is the probe broken? How can this state be fixed? Regards, Axel -- Axel Fischer Network Engineer 1&1 Internet AG Brauerstrasse 48 D-76135 Karlsruhe http://www.1und1.de (AS8560) Hauptsitz Montabaur, Amtsgericht Montabaur, HRB 6484 Vorstand: Ralph Dommermuth, Frank Einhellinger, Robert Hoffmann, Andreas Hofmann, Markus Huhn, Hans-Henning Kettler, Uwe Lamnek, Jan Oetjen, Christian Würst Aufsichtsratsvorsitzender: Michael Scheeren Member of United Internet Diese E-Mail kann vertrauliche und/oder gesetzlich geschützte Informationen enthalten. Wenn Sie nicht der bestimmungsgemäße Adressat sind oder diese E-Mail irrtümlich erhalten haben, unterrichten Sie bitte den Absender und vernichten Sie diese Email. Anderen als dem bestimmungsgemäßen Adressaten ist untersagt, diese E-Mail zu speichern, weiterzuleiten oder ihren Inhalt auf welche Weise auch immer zu verwenden. This E-Mail may contain confidential and/or privileged information. If you are not the intended recipient of this E-Mail, you are hereby notified that saving, distribution or use of the content of this E-Mail in any way is prohibited. If you have received this E-Mail in error, please notify the sender and delete the E-Mail.

3 2

Probe sharing
by Martin Stanislav 08 Aug '13

08 Aug '13

Hi, This spring RIPE Atlas update [1] introduced a new feature called probe sharing. Probe sharing should work for colleagues within the same LIR and is to be set via: "My Probes" -> "Probe's Settings" -> "General Configuration" -> Select your LIR in the "Share with" field. I've set the "Share with" field to our LIR ID for all three local probes. But a colleague of mine, in spite of being able to login to the Lirportal, sees an error message below every time he tries to access the probe list at https://atlas.ripe.net/atlas/myprobes.html The error message: "You are not logged in as a RIPE NCC member". Is there anything I've missed? Possible delay in privilege propagation from the Lirportal to Atlas section? Thanks. Martin [1] https://labs.ripe.net/Members/kistel/new-ripe-atlas-features-april-2013

4 4

Multiple Probe v3 Disconnects
by David Churchill 08 Aug '13

08 Aug '13

I just received my v3 probe 3 days ago and I've noticed on the status page that that there are quite a few disconnects: Disconnect at: Connected time: Disconnected time: (still connected) 0d, 0h, 30m (still connected) 2013-08-08 11:37:44 UTC 0d, 0h, 38m 0d, 0h, 2m 2013-08-08 10:49:09 UTC 0d, 1h, 14m 0d, 0h, 10m 2013-08-08 09:31:38 UTC 0d, 2h, 2m 0d, 0h, 3m 2013-08-08 07:25:41 UTC 0d, 1h, 22m 0d, 0h, 3m 2013-08-08 05:53:24 UTC 0d, 1h, 26m 0d, 0h, 9m 2013-08-08 04:24:56 UTC 0d, 2h, 23m 0d, 0h, 2m 2013-08-08 01:57:23 UTC 0d, 1h, 18m 0d, 0h, 4m 2013-08-08 00:35:09 UTC 0d, 0h, 26m 0d, 0h, 3m 2013-08-08 00:05:53 UTC 0d, 1h, 25m 0d, 0h, 2m 2013-08-07 22:37:14 UTC 0d, 1h, 12m 0d, 0h, 3m 2013-08-07 21:20:56 UTC 0d, 0h, 4m 0d, 0h, 4m 2013-08-07 21:11:44 UTC 0d, 2h, 9m 0d, 0h, 4m 2013-08-07 18:59:32 UTC 0d, 0h, 39m 0d, 0h, 2m 2013-08-07 18:18:40 UTC 0d, 6h, 12m 0d, 0h, 1m 2013-08-07 12:03:56 UTC 0d, 12h, 42m 0d, 0h, 1m 2013-08-06 23:19:16 UTC 0d, 0h, 4m 0d, 0h, 2m 2013-08-06 23:15:08 UTC 0d, 0h, 2m 0d, 0h, 0m 2013-08-06 23:05:16 UTC 0d, 4h, 45m 0d, 0h, 7m 2013-08-06 18:17:13 UTC 0d, 1h, 54m 0d, 0h, 2m 2013-08-06 16:18:39 UTC 0d, 0h, 45m 0d, 0h, 3m 2013-08-06 15:32:39 UTC 0d, 0h, 41m 0d, 0h, 0m 2013-08-06 14:50:33 UTC 0d, 2h, 32m 0d, 0h, 0m 2013-08-06 05:51:43 UTC 0d, 6h, 47m 0d, 6h, 25m Is this something I should be concerned about? If so, could it have to do with the fact that my probe is plugged into a 10/100/1000 MBit switch (I saw an earlier thread that suggested this might be an issue)? If the Gigabit switch is a problem, would it help if I cascade a 10/100 switch off one of the Gigabit switch's ports, or off one of my router's ports (which are all Gigabit) and then plug the probe into that 10/100 switch? Finally, I'm using a cell phone charger for power, it's 5V, mini-usb, I don't think that should cause an issue should it? Thanks for any help, David C. Churchill 5285 Vinings Springs Trl Mableton, GA 30126 770.819.5935 d_churchill(a)comcast.net

3 4