- ripe-atlas - mailman.ripe.net

Probe cannot connect from behind IDS/IPS with HTTPS inspection
by Ondřej Caletka 21 May '14

21 May '14

Hello list, I just observed strange behaviour of one Atlas probe. It was unable to connect to the control server from a corporate network. I suspect that some IDS/IPS appliance detects and drops probe attempt to use port 443 for non-TLS traffic*. I've tested it by trying to SSH to control server from within that network and it failed. However, normal SSH to port 22 works fine. It would be nice if the probe would be able to try more ways to reach the control server, eg. first attempt on port 443, second on port 22, third on some arbitrary high port number. I know that it would be better to put the probe in front of the firewall/IPS, but this is much more complicated in many corporate networks. *) At least it doesn't do MitM on HTTPs traffic. I've checked that too. Cheers, Ondřej Caletka

6 10

a thought about public probe page...
by Wilfried Woeber 21 May '14

21 May '14

I've got a small comments regarding the probes' overviw page at https://atlas.ripe.net/probes/ - for the country filter, top right, could the list of countries be sorted? Thanks, low prio :-) Wilfried.

1 0

Problems with DNS measurements and NSID
by Klaus Darilion 21 May '14

21 May '14

Hi! Whatever I try I fail to get the nameserver id. See measurement: https://atlas.ripe.net/api/v1/measurement/1666014/ But there is no NSID in the results: https://atlas.ripe.net/api/v1/measurement/1666014/result/ Am I doing something wrong, or is there a bug? Thanks Klaus

5 12

NTT Communications (US, Miami) has joined RIPE Atlas anchors
by Michela Galante 20 May '14

20 May '14

Dear RIPE Atlas users, We're happy to announce that another RIPE Atlas anchor has joined the network and is now available as a target for probe hosts conducting their own user-defined measurements. The new anchor is called us-mia-as2914 and it is hosted by NTT Communications in Miami, United States. Congratulations to NTT Communications for their second anchor online! 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

high volume IPs/anycasted?
by Jared Mauch 19 May '14

19 May '14

I have a few IPs on our network that are anycasted that I'd like to see the "9 limit" increased for, is there a proper way to do this? - Jared

1 0

Some UDM comments
by Jared Mauch 19 May '14

19 May '14

I'm working on creating some measurements and haven't quite moved into using the API yet and wanted to provide some feedback: 1) When creating a UDM, when it's scheduled but not yet assigned to probe(s), it would be nice to be able to increase the # of probes. 2) When creating a UDM and specifying source ASN, you can't type in that box and must use the pull-down. Related to #1, if you increase probes to (eg: 5) it resets to 1 after you select the ASN. 3) When stopping a UDM that is set for ongoing/no-end, it would be nice to have a 'stop now' vs having to pick the next 15 minute interval. In theory the system could auto-populate this. 4) I do like the probes/map/seismograph view, is it possible to provide a direct-link to these public UDMs without logging-in? (I haven't looked closely so there may be a way to do this). Trying to not need to fetch the data and generate my own graphs... 5) If I see a probe that is behaving poorly, eg: UDM 1665566 Probe# 3925, should I be providing feedback on this to others? I'm working on a Nx(N-1) measurement of these ASNs to determine which have persistent congestion that can be measured via RIPE Atlas if that is of interest to others. 174 209 701 1239 1299 2828 2914 3320 3257 3356 3491 3561 5511 6453 6461 7018 Those interested in this, I will be able to send you a list of UDMs to look at which are public. - Jared

4 4

NTT Communications (US) joined RIPE Atlas anchors
by Michela Galante 19 May '14

19 May '14

Dear RIPE Atlas users, We're happy to announce that another RIPE Atlas anchor has joined the network and is now available as a target for probe hosts conducting their own user-defined measurements. The new anchor is called us-dal-as2914 and it is hosted by NTT Communications in Dallas, United States. 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

Taking the fuzz our of client cache results
by Mark Delany 17 May '14

17 May '14

Hi. I've been running some DNS queries using the probe caches with a view to understanding the latency between the probe cache and the authoritative that I'm interested in. The problem is that there is a fair degree of uncertainty in these measurements because the cache may have to first resolve higher level names in the hierarchy and there is no way of knowing whether the cache had to do this or not. If my query is for www.example.com, it's quite possible that the cache has to first resolve example.com prior to sending the final query for www. This means the measurement may include the cost of getting an answer from .com *and* getting the answer from example.com... sometimes. Depending on how popular example.com is and what other clients are doing with the cache. I'm wondering if there is a way in which we can eliminate this fuzziness? The most obvious way to do this is to ensure the cache is pre-primed with every answer up to, but not including the target name. If we assume the measurement request includes a new "prime cache" flag, then in the presence of that flag the probe could first run a query for something like: cacheprime.example.com substituting the first label with some other value. Alternatively it could first run an NS query for example.com A third alternative is that the creator of the measurement could nominate the priming query as they will have the knowledge needed to get it right. A forth alternative is that the probe could run the query twice - with a nominated delay that is known to exceed the TTL of the target query. In all cases, as soon as the priming query is complete, the probe then runs the target query with a high degree of confidence that the cache only needs to make one round trip to the authoritative server. There is still a small probability that the results will be fuzzy for a variety of reasons, multiple cache choices, anycast caches, super-busy caches, multiple probes using the same cache, but that probability will be very low. Also, a pre-primed query would presumably cost twice as many credits since it's really running two queries. Do others think a primed cache query is of use? And, are there ways of achieving this already? Mark.

2 2

Atlas API and IPv6
by Daniel Gomez 14 May '14

14 May '14

Hi All, Could it be that the API at atlas-ui.ripe.net is since last night not ipv6 reachable? We are not sure if it was before, but we had to change today the DNS Name to the ipv4, in order for the requests to work. Thanks in advance, Daniel El 14/05/2014 11:45, "Vesna Manojlovic" <BECHA(a)ripe.net> escribió: > Dear colleagues, > > There have been a lot of great examples recently of how RIPE Atlas can be > used to investigate network events, troubleshoot problems, explore how the > Internet behaves, and more. Some of the topics include: > > - Investigating customer complaints about slow servers > - Comparing TCP and UDP Response Times of DNS Root Servers > - Discovering Path MTU black holes on the Internet > > We’ve collected all of these user experiences, analyses, papers and > presentations in one place on RIPE Labs, in order to make it easy to > discover how others are making use of the RIPE Atlas network - and maybe > spark some ideas about how you can, too. > > https://labs.ripe.net/atlas/user-experiences > > If you have your own story about how you’ve used RIPE Atlas, we want to > hear from you! Please get in touch with us at atlas(a)ripe.net , > or on this list. > > Kind regards, > > Vesna Manojlovic > Measurements Community Building > RIPE NCC > > > > >

2 1

RIPE Atlas use cases and more
by Vesna Manojlovic 14 May '14

14 May '14

Dear colleagues, There have been a lot of great examples recently of how RIPE Atlas can be used to investigate network events, troubleshoot problems, explore how the Internet behaves, and more. Some of the topics include: - Investigating customer complaints about slow servers - Comparing TCP and UDP Response Times of DNS Root Servers - Discovering Path MTU black holes on the Internet We’ve collected all of these user experiences, analyses, papers and presentations in one place on RIPE Labs, in order to make it easy to discover how others are making use of the RIPE Atlas network - and maybe spark some ideas about how you can, too. https://labs.ripe.net/atlas/user-experiences If you have your own story about how you’ve used RIPE Atlas, we want to hear from you! Please get in touch with us at atlas(a)ripe.net , or on this list. Kind regards, Vesna Manojlovic Measurements Community Building RIPE NCC

1 0