- ripe-atlas - mailman.ripe.net

Incorrect probe connection information?
by Max Mühlbronner 13 Apr '16

13 Apr '16

Hi, I think there is a small bug/issue with the statistics of the probe (Tab : "Network") : Connection Information Time Connected Percent Last Week 9d 10h 2m 100.00% Last Month 55d 10h 2m 100.00% How could it be that Last Month my probe was connected for 55 days? (It's only a single probe) Any idea? Best Regards Max M.

3 3

Introducing the RIPE Forum
by Vesna Manojlovic 12 Apr '16

12 Apr '16

Dear colleagues, There’s a new way to participate on the RIPE Atlas mailing list! We are introducing the RIPE Forum, a web-based interface for reading and sending emails on RIPE community mailing lists. We developed the RIPE Forum in-house based on feedback we received from members of the RIPE community who wanted the option to interact and share information in a more modern way. But it’s important to note that this new interface is completely optional – those who like using the established mailing list system can continue on as they always have, and won’t notice any difference. RIPE Atlas mailing list will be the first one. We have plans to make the RIPE Forum available for other RIPE Community mailings lists after the RIPE 72 Meeting in May. If you’re interested, you can start using it here: https://www.ripe.net/participate/mail/forum/ We created a special mailing list for testing purposes, so that any conversations about the platform itself can be contained there without disrupting the regular flow of discussions on the RIPE Atlas mailing list. Feel free to send test messages and try out the RIPE Forum on this special list: https://www.ripe.net/participate/mail/forum/ripe-forum-test Learn more how the forum works and the background of the project: https://labs.ripe.net/Members/marco_schmidt/introducing-the-ripe-forum The forum is still in "beta" status – there are likely still some bugs and we are continuously working to improve things, so please keep that in mind while exploring the forum. You can give your feedback by clicking on the “Report a bug” button on the forum, or leave a comment on the above RIPE Labs article. We hope you’ll enjoy the RIPE Forum, and look forward to your feedback! Kind regards, Vesna Sent via RIPE Forum -- https://www.ripe.net/participate/mail/forum

3 2

change stop date?
by gboonie 11 Apr '16

11 Apr '16

Hi, In the past, when you scheduled a measurement for some weeks, you could change the end date. This does not seem possible any more. Is that intentional? Could that be changed please? Also, can't we change measurements to private anymore? The field is there to show that it is public, but changing does not seem possible anymore. Thanks, Dave

1 0

Local network checks
by Alison Wheeler 11 Apr '16

11 Apr '16

Recently my probe stopped responding to RIPE even though it was pingable through the local network. Putting aside what the cause might have been* is there any way to 're-awaken' or cycle in some way a probe without physical access to it? (* sfaict it didn't restart when the USB socket on the server it takes power from was remotely restarted) Sent via RIPE Forum -- https://www.ripe.net/participate/mail/forum

3 9

Failing 4GB USB on v3 probes?
by Phillip Remaker 11 Apr '16

11 Apr '16

So far, I have had two of the SanDisk Cruzer 4GB drives (SDCZ33) fail, and I think I have two other ML-3020 (v3) devices with the same fate. Case #1, the drive fell into read only one. Case #2, the drive identifies to the USB, but read of block 0 (capacity) fails. The first time I called SanDisk and jumped through their hundred hoops to replace it.They were reluctant since I couldn't produce a receipt. This time, I just grabbed an old 8GB USB and dropped it in. Looks like it only uses 3GB. Does Atlas plan to pursue warranty claim, or is this an acceptable failure level for the probes?

2 1

Flow-id of built-in traceroute measurement
by Wenqin SHAO 08 Apr '16

08 Apr '16

Dear list, I have some questions concerning the flow-id of built-in traceroute measurements and are seeking for your help. As many of you may have already noticed, the flow-id of the built-in traceroute measurement periodically varies form 0 to 15, in a circular manner. With this behaviour, it is supposed to reveal the diversity of underlying IP paths. In the case that there are more than 16 unique IP paths between a source and destination pair, could this scheme reveal all of these IP paths? If it can, which leads to more than one IP paths per flow-id? Is it normal, from a load balancer point of view? If it can not, then why not a wider range of flow-id (more nuances in header hash results), say [0, 63]? Is it related to common realisation of load balancer? Many thanks in advance. Best regards, Wenqin ==== Wenqin SHAO PhD Candidate Telecom ParisTech

2 2

Scheduling a test for all probes?
by Jared Mauch 06 Apr '16

06 Apr '16

Is there a way to schedule a one-off test on all the probes to be run “at a leisurely pace”, eg: looking up a specific DNS QNAME? (I’ll call it a lazy query/scheduling). - Jared

3 2

Research using RIPE Atlas probes: How Pingable are the Pingables?
by Vesna Manojlovic 05 Apr '16

05 Apr '16

Dear colleagues, take a look at how the "pingable:" and "ping-hdl:" attributes have been adopted in the last five years and how reachable the pingable addresses registered in the RIPE Database are when pinged from RIPE Atlas. Spoiler alert: It could be better. Please find the details on RIPE Labs: https://labs.ripe.net/Members/wilhelm/how-pingable-are-the-pingables Kind regards, Vesna

1 0

Credits sharing and other new features
by Vesna Manojlovic 04 Apr '16

04 Apr '16

Dear colleagues, many of you have been asking for the credits sharing options, and now we have added two new ways that you can go about it: - standing orders - share access - and the transfers are still possible too All about credits: https://atlas.ripe.net/docs/credits/ In addition to that, in the past few months, we've added some other new features and functionality to RIPE Atlas, including making the DNSMON code available on GitHub for personal use, displaying IPv4 vs IPv6 comparisons in LatencyMON, and new limits on probes per measurement and results per day. Learn more about the latest updates on RIPE Labs: https://labs.ripe.net/Members/suzanne_taylor_muzzin/ripe-altas-update-dnsmo… Regards, Vesna

2 1

Re: [atlas] [ripe.net #1204062] request to add three more ccTLDs to, DNSMON: CR, SG, and TW
by Romeo Zwart 04 Apr '16

04 Apr '16

Hi Peter, You have recently requested to have three ccTLD zones be added to DNSMON. Unfortunately, since the zones do not fall into the RIPE service region and the zone owners are not members of the RIPE NCC, the request does not qualify according to ripe-661. If the zone owners do wish their zones to be monitored by DNSMON we need to ask them to become members of the RIPE NCC. Alternatively they could argument an exception for their case with the DNS working group. Apologies for the confusion. Feel free to contact us if you have further questions. Kind regards, Romeo -------- Forwarded Message -------- Subject: Re: [ripe.net #1204062] request to add three more ccTLDs to DNSMON: CR, SG, and TW Date: Mon, 04 Apr 2016 10:39:21 +0200 From: pk(a)denic.de <atlas(a)ripe.net> Reply-To: atlas(a)ripe.net CC: becha(a)ripe.net, mgalante(a)ripe.net Hi Alastair, On Thu, Mar 31, 2016 at 11:40:48AM +0200, Alastair Strachan wrote: > Could you please provide me with the points of contact who gave you their consent for an independent verification? sure, we'll dig it out of our ticketing system. Regards, Peter

1 0