- ripe-atlas - mailman.ripe.net

Six new RIPE Atlas anchors are now active
by Michela Galante 01 Dec '13

01 Dec '13

Dear RIPE Atlas users, We're happy to announce that six more RIPE Atlas anchors have joined the network: us-pao-as5580 is operated by Atrato Networks in Palo Alto, United States us-ewr-as5580 is operated by Atrato Networks in New York, United States de-fra-as5580 is operated by Atrato Networks in Frankfurt, Germany nl-dft-as31019 is operated by Meanie in Delft, Netherlands fr-sxb-as8839 is operated by SdV Plurimedia in Strasbourg, France nl-ams-as3333-2 is operated by RIPE NCC in Amsterdam, Netherlands Anchoring measurements (ping, ping6, traceroute and traceroute6) are scheduled towards these anchors 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/ We would like to thank Job, Paul and Salim who put in a lot of effort to become the first anchor hosts! Kind regards, Measurements Community Building Team RIPE NCC mcb(a)ripe.net

4 5

Space.net (DE) has joined RIPE Atlas anchors
by Vesna Manojlovic 28 Nov '13

28 Nov '13

Dear RIPE Atlas users, We're happy to announce that another RIPE Atlas anchor has joined the network. The new anchor is called de-muc-as5539 and is operated by Space.net in Munchen, 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

First RIPE Atlas anchor since production service now active
by Vesna Manojlovic 28 Nov '13

28 Nov '13

Dear RIPE Atlas users, We are proud to announce that the first RIPE Atlas anchor since this new service went into full production came online yesterday! It is situated in Munich, Germany, and is operated by Space.net. Congratulations on being the first one! Our thanks go to Gert Doering, who put in a lot of effort working alongside the RIPE NCC team through the new procedure, as well as to five other new hosts whose anchors will be activated tomorrow. From now on, we will announce each new anchor as it is activated, together with the anchoring measurements towards them. All RIPE Atlas anchors can be seen on this list and map: https://atlas.ripe.net/anchors/list/ https://atlas.ripe.net/anchors/map/ Kind regards, Vesna Manojlovic Measurements Community Building RIPE NCC

1 0

New on RIPE Labs: Map a RIPE Atlas Anchor
by Vesna Manojlovic 27 Nov '13

27 Nov '13

Dear colleagues, Please find a new article, contributed by Daniel Karrenberg, on RIPE Labs: RIPE Atlas Fun - Map a RIPE Atlas Anchor. https://labs.ripe.net/Members/dfk/map-a-ripe-atlas-anchor It shows some interesting graphs based on RIPE Atlas traceroute measurements. Kind regards, Mirjam Kuehne RIPE NCC

1 0

feature requests
by Mike. 25 Nov '13

25 Nov '13

Philip Homburg Fri Nov 22 11:08:39 CET 2013 > >Hi, > >>On 2013/11/11 19:32 , Mike. wrote: >> Allow me to disable the processing of RA's on IPv6, so that I >> can configure IPv6 statically and not have it overwritten by an >> RA. > >This feature has been requested by a handful of people. However, this >introduces more complexity in the already way too complex network >configuration of the probes. So we like to avoid implementing this >feature. Of course if there is wide spread demand for it, then we will >look into it. > >I should try it sometime, but in theory one way to give the static >address priority is to set all prefixes in the RA to deprecated. On a >'normal' network where you one prefix, it should not make a difference >for any of the other hosts. > >Philip Hi Philip, In the context of ~~I don't know what is going on inside the Atlas probe, so I'll presume an easy solution~~ ... WOuldn't a solution be to just disable the rtsol daemon when static IPv6 addresses are configured? If the probe does not issue a router solicitation request, then it won't receive RA's. Seems to me that somewhere there is a rtsol=enable that could be changed to rtsol-disable and that would resolve the issue. Configuration would still need to be done via IPv4 using DHCP in this instance. But that process is already well documented. As always, thanks for listening. Mike.

1 0

RTT Graphs for UDMs
by Alex Saroyan 25 Nov '13

25 Nov '13

Hi, As far as I understand there is no RTT history/graph for UDMs. I think it could be very usefull to have a graph storing maybe 1-6 month history of RTT for UDMs. I would really appreciate to have such a history of certain RTT values and the look for correlation with operational changes. -- Regards. /Alex Saroyan

1 0

HTTP/HTTPS probe
by Max Tulyev 22 Nov '13

22 Nov '13

Hi All, What about HTTP/HTTPS requests from Atlas probes? I hear it is technically possible. This test can provide statistics about quality and availability of certain websites, as well as the information about content is delivered unmodified, not blocked, correctly/incorrectly cached, etc. Is it possible to enable that kind of probes?

10 15

Very short uptime for some probes
by Mark Delany 22 Nov '13

22 Nov '13

Hi all. I've only been on this list for a relatively short while so this is most likely in an FAQ I should be digging thru... I've noticed that the uptime for some of the physical probes we've installed are very short. According to the control panel, one in particular has connect times of around 2-3 minutes and disconnect times of 4-6 minutes. This cycle is repeated every 10 minutes or so. All day, every day. Superficially that sort of pattern suggests some sort of continuous reboot loop. However, if I ping the probe remotely, I get just an occasional packet loss. Certainly no long gaps that you'd expect from a continuous reboot. That I can ping it remotely also suggests that external connectivity isn't the problem. Besides the periodicity is just too regular and frequent for a routing loss or similar. (In any event, if the network it's on is losing connectivity every 5 minutes I would have plenty of other symptoms.) The problem probe is also reported as getting UDMs assigned and running them so I'm not quite sure how it manages to squeeze those tests in if that connectivity status report is accurate. So my main question is, should I be concerned about the control panel connectivity reports? And if I should be, is there much I can do beyond ensuring the device has good connectivity? Mark.

3 6

Categorize probes (feature request)
by Klaus Darilion 22 Nov '13

22 Nov '13

Hi! Depending on the measurement, sometimes I want a realistic "user's view" which means using probes in residential areas, and sometimes I want a "backbone" view, which mean using probes in the back-bone (good connected) e.g. to measure my access network or my servers without the delay introduced by the probes access network. Thus, it would be cool if the probe selection algorithm allows also to choose "residential" probes or "backbone" probes. Maybe this categorization can be done automatically, or probe owners can be asked to specify the probes connectivity manually. Thanks, Klaus

11 26

UI displays of measurements
by Gilles Massen 22 Nov '13

22 Nov '13

Hi, When you visualize a measurement in the GUI, what data is used for tabs like "Probes" or "Map"? Is that the latest available data from each participating probe, or something else? Gilles -- Fondation RESTENA - DNS-LU 6, rue Coudenhove-Kalergi L-1359 Luxembourg tel: (+352) 424409 fax: (+352) 422473

3 3