- ripe-atlas - mailman.ripe.net

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

Change account email address
by Mike. 22 Nov '13

22 Nov '13

Hi, Is there a way to change the email address that is used to log in to the RIPE Atlas site? I am talking about the email address that is the answer to the prompt: Sign in using your RIPE NCC Access account and not the alert email address used when the probe goes offline for a period of time. Thanks, Mike.

4 5

Sudden raise in UDM credit consumption
by Tarko Tikan 20 Nov '13

20 Nov '13

hey, Has there been a change how UDM probe prices are calculated? I stopped old UDM (1004320) that had following parameters: - v4 ping - 10 probes - 240 seconds, 3 packets, size 500 - 3.0 credits per result, 10800 credits per day When I created identical UDM (1040516) (UDM parameters should really be changeable to there should be possiblity to clone UDM and then modify all parameters) with double amount of probes (20) and same parameters, I'm now suddenly charged 31.25 credits per result. This does not follow the linear logic as only parameter that changed is number of probes. -- tarko

2 2

Power plugs for the Anchor nodes
by Job Snijders 15 Nov '13

15 Nov '13

Dear all, A moment of clarity occurred to me, just before I shipped out some anchor nodes: the power plugs on the back of box (C7 type) won't easily be connected in most datacenter deployments. I found these cute plugs [1], which can be ordered here [2]. Hope this helps others :-) How have others solved the issue? Any ideas on how to get these Anchors to run on 48V DC (for telco-style deployment)? Kind regards, Job [1] - http://www.kempelektroniks.nl/FilesContent/menu/menu000250/images_iecc7adap… [2] - http://shop.kempelektroniks.nl/index.php/accessories/iec-adapters.html

4 3