- ripe-atlas - mailman.ripe.net

Easy LG-style ping/traceroute interface?
by Roman Mamedov 19 Mar '13

19 Mar '13

Hello, I would like to suggest for RIPE to implement a simple "Looking Glass" style interface to run one-time measurements (ping and traceroute) on probes. If anyone doesn't know what Looking Glass is, some examples are http://lg.he.net/ , http://www.oneasiahost.com/lg/ , http://cl.edis.at/ etc. Key features of such Atlas interface would be: - Interface similar to generic "Looking Glasses" as those mentioned above; - Allow access to general public, not requiring registration or login (maybe with some rate-limiting on requests); - Allow running ping and traceroute from any probe (or maybe only from a subset, hosts of which express a desire to participate in this public LG subproject), to any arbitrary IPv4/v6/hostname destination; - One-shot execution only (not scheduled checking over time, like the current measurements); - Real-time returning of the results(!); this might be tricky, it means a RIPE server will need to have means to instantly connect to the selected probe, ask it to perform a measurement and then retrieve results, all in "online" real-time mode. This might exclude probes which are behind a NAT and without IPv6 or with strict firewalling. -- With respect, Roman

2 1

Include country code in UDM "Last 100"
by Adam Piggott 06 Mar '13

06 Mar '13

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, I've just run my first UDM for a real-world diagnostic test. Very helpful! If the "Last 100" list data contained a country code column it would be helpful - especially when trying to track down a possible routing problem that may be related to the originator country. It would also be quite helpful to be able to add participating probe criteria using a negative, for example: "not GB, not US". Regards, - -- Adam Piggott, Proprietor, Proactive Services (Computing). http://www.proactiveservices.co.uk/ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (MingW32) iEYEARECAAYFAlE2NmYACgkQ7uRVdtPsXDnHQACggHcxMZVmwodiNdwuZ48KATgz itIAn2Bk8F0rbS02WbHhl9NUlkZH+R27 =DTMB -----END PGP SIGNATURE-----

2 1

RIPE66 and another Atlas BoF?
by Vesna Manojlovic 05 Mar '13

05 Mar '13

Hi everyone, RIPE meeting in Dublin is approaching fast, and we are preparing for it full speed... ... which brings me to you - the RIPE Atlas Community! Will you be there? Do you want to have another BoF session? Would you like to share some of your experiences - with measurements, results, visualizations, success stories, use cases... Do you have questions to ask developers - tricks & tips, new features, favorite option that is missing? Few of the RIPE Atlas "staff" (RIPE NCC staff) will be there, we are available to talk with you in the hallways and during drinks, we will be giving official updates & presentations... ... but if you want the meeting of like-minded users and contributors, please do let me know, and I will request a BoF slot again. Cheers, Vesna http://ripe66.ripe.net

1 0

New version of probe firmware released: 4500
by Vesna Manojlovic 28 Feb '13

28 Feb '13

Dear probe hosts and community, few days ago we released the new version of RIPE Atlas probe firmware: 4500. These are the technical details: * RIPE Atlas probe software now supports two more architectures: TP-Link (for the next generation probes) and CentOS (for RIPE Atlas anchors). * There is now support for one-off measurements for ping, traceroute, DNS, and HTTPget. * We fixed a bug in DNS measurements in which, when querying local resolvers, more queries went to the last resolver. * Fixed "error" : { "TUCONNECT" : "Success"}. Before this version DNS TCP and HTTPget reported an error message "Success". When enough probes have been automatically upgaded to this new firmware, this will enable us to start testing the "one-off" or "near-real-time" measurements. We will enable this first for beta-testers, and after we fix the bugs reported by them, we will mae it available to all probe hosts, sponsors, and RIPE NCC members. Regards, Vesna

1 0

Notification regarding corrections to credit balances.
by Daniel Quinn 19 Feb '13

19 Feb '13

Dear all, We'd like to inform you that we've recently discovered a bug in our accounting process that has caused some of you to be allocated fewer credits than you deserve. We've fixed the bug today. We are now calculating exactly how many credits have not been accounted for, and we will be crediting everyone's accounts accordingly. We apologise for the mix up, and if you have any questions, please feel free to ask.

1 0

Warnings about running out of credits and runaway measurements
by Robert Kisteleki 18 Feb '13

18 Feb '13

Dear Atlas users, Today we're going to enable two features that have been forecasted in the January 2013 Atlas update (https://labs.ripe.net/Members/becha/ripe-atlas-january-2013-achievements) Both of these features are intended to prevent runaway measurements which consume system resources, and to limit the resources used by users who don't contribute (any more) to the system; thus they both contribute to the stability and scalability of RIPE Atlas. They are both controlled by the credit system. The first feature is about sending warning emails if someone is about to run out of credits. That is, if the current credit consumption rate (with a two day lookback period) seems to use up all credits of a particular user within the next week or so, then we'll send an email about this. This allows the user to organise some extra credits, or stop some less important measurements in due time. The second feature stops measurements if someone actually runs out of credits. For now we'll use a *warning only* mode -- that is, the process will not actually stop measurements, it will only send emails. After a couple of weeks we'll change this to actually stop (some of the) measurements as well as notify the user. Our tests show that at the moment there are about a dozen people who would see effects of these processes. Both of these are necessary steps towards removing the existing limits imposed by the system (such as maximum amount of probes that can be used). Please let us know if you have questions or concerns, either on this mailing list, or (privately) by sending a mail to atlas(a)ripe.net Best regards, Robert Kisteleki RIPE Atlas team

1 0

Phase 1 of RIPE Atlas Anchors pilot - report on RIPE Labs
by Vesna Manojlovic 15 Feb '13

15 Feb '13

Dear community, [apologies for the duplicates] we just published an article on RIPE Labs with the status & features available for the hosts of RIPE Atlas Anchor boxes after the Phase 1: https://labs.ripe.net/Members/becha/ripe-atlas-anchors-pilot-update-on-phas… Share and enjoy :) Vesna

1 0

UDM destinations also visible in RIPEstat
by Vesna Manojlovic 13 Feb '13

13 Feb '13

Hi, I just wanted to share one more RIPE Atlas-related feature of RIPEstat: when querying for a IP prefix or AS number, you can now see all the UDMs that terminate in the IP addresses in that ASN or prefix, in the "Activity" tab, called "RIPE Atlas measurements targets". (picture attached) Below is a reminder of the feature to see all the probes, too. Happy measuring! Vesna -------- Original Message -------- Subject: [atlas] Atlas probes visible in RIPEstat Date: Fri, 21 Dec 2012 10:11:26 +0100 From: Vesna Manojlovic <BECHA(a)ripe.net> To: RIPE Atlas People <ripe-atlas(a)ripe.net> Dear RIPE Atlas users, this might be of interest to you too -- it is now possible to see coverage of Atlas probes in any ASN, prefix or *country* in RIPEstat! It works both as a widget and as CLI: https://stat.ripe.net/widget/atlas-probes#w.resource=212/12 or whois -h stat.ripe.net AS3333 If you decide to embed this widget somewhere on your page, please do let us know, we like to see our work being used :) More interesting RIPEstat features in the article on RIPELabs: https://labs.ripe.net/Members/suzanne_taylor_muzzin/ripestat-2012-december-… Cheers, Vesna

1 0

RIPE Atlas Community repository on GitHub
by Vesna Manojlovic 08 Feb '13

08 Feb '13

Hi everyone, an appropriate pastime for Friday afternoon - playing with GitHub ;-) I initially created https://github.com/RIPE-Atlas-Community/ripe-atlas-community-contrib for the contributions by you (and atlas-dev team) of the small programs, scripts, etc -- for visualizing RIPE Atlas measurements, analysing measurements data, and so on. We already had them listed here: https://atlas.ripe.net/doc/code However, GitHub seems to be *the* place for the community to exchange the code, so I am hoping that this repository will help share and maintain, and produce more code, and make it more useful for the rest of the world. First code in there is the one I inserted, created by Philip Homburg: "probes2kml.py", that shows probes on Google Earth. Please "add" more, or "link" your own contributions to this repository... ... or let me know how I can help to collect more of the RIPE Atlas specific code to this repository: from Wolfgang, Inigo, and others. Share and enjoy :) Regards, Vesna

1 0

Partial downtime over the weekend
by Robert Kisteleki 04 Feb '13

04 Feb '13

Dear all, On Friday we added the first devices of the upcoming next generation Atlas probes to our production network. Unfortunately, this triggered a bug in our controlling infrastructure, which resulted in some of the probes not being assigned any new measurements. Eventually, the affected probes ran out of measurement tasks. This bug affected about 30% of the probes approximately between Friday 23h and Sunday 12h (UTC). We apologise for any inconveniences this may cause. Regards, Robert Kisteleki RIPE Atlas team

1 0