- ripe-atlas - mailman.ripe.net

DNS over TCP problems?
by Stephane Bortzmeyer 21 Mar '17

21 Mar '17

[I did not test it myself.]

2 4

Trivia of the day: Atlas probes and alternative DNS roots
by Stephane Bortzmeyer 21 Mar '17

21 Mar '17

A quick test with a thousand probes seem to indicate that less than a dozen of all the probes use an alternative DNS root (or, more stricly, use a DNS resolver which is configured for an alternative root). The only alternative root used seems to be OpenNIC. Measurements #7865679 #7865870 #7865872 #7865873

1 1

Fwd: [mat-wg] Atlas: DNS TCP Errors
by John 14 Mar '17

14 Mar '17

Hello Atlas, feature request, when preforming DNS queries over TCP would it be possible for the probe to differentiate between a timeout and a TCP Reset. Currently the result just records the following when it gets a reset[1]. `error.timeout: 5000` A similar feature to record ICMP prohibited for udp queries would also be useful but likely much harder. Thanks John [1]https://atlas.ripe.net/api/v2/measurements/7859749/results?start=14888448…

3 3

Lowercase country codes in the probes database
by Marat Khalili 14 Mar '17

14 Mar '17

While using use probes database at ftp://ftp.ripe.net/ripe/atlas/probes/archive/ I noticed that 33 probes have country_code values in lower case (e.g. "ru" instead of "RU"), some in "Connected" state. When trying to distribute probes evenly among available countries it obviously affects the result. Of course, it's easy to work around once you are aware of this 'feature', but I only found the problem by chance. I wonder what's the story behind this and can this be fixed? (Web-interface doesn't seem to be affected.) -- With Best Regards, Marat Khalili

2 1

RIPE Atlas Infrastructure Maintenance (14 March)
by Paul de Weerd 13 Mar '17

13 Mar '17

Dear all, We'll carry out maintenance work on the core RIPE Atlas and RIPEstat infrastructure tomorrow (14 March 2017), approximately between 09:00 and 11:00 UTC+1. As a result, we will switch over to the reduced data set, limiting the amount of history available from the service. This affects RIPE Atlas, RIPEstat, RIS and DNSMON. We apologise for the inconvenience. Best regards, Paul de Weerd Senior Systems Engineer RIPE NCC

1 0

Surplus RIPE Atlas credits
by Michael Reutter 13 Mar '17

13 Mar '17

Hi everyone, I host a probe but at the moment I do not create measurements. As such, I have a large surplus of unused credits. Is anyone in need of credits and would like for me to transfer them? Best, Michael

1 0

Probe: Any benefits to set in DMZ?
by Martin Boissonneault 13 Mar '17

13 Mar '17

Hi! Is there any benefit to put the Probe in a home router "DMZ"? I could not find the answer in the FAQ. My setup is: 1- The Probe is directly connected to the ISP all-in-one router in it's DMZ (Bell Home Hub 3000, FTTH). 2- My personal router is directly connected to the ISP router, but connecting through PPPoE passthrough. Both routers have different ISP IPs. The ISP router is used for the Fiber SFP module, TV and phone. The Probe takes internet from the ISP router, but nothing else. Thanks, Martin Boissonneault Sent via RIPE Forum -- https://www.ripe.net/participate/mail/forum

4 4

More even earth distribution of measurement probes
by Marat Khalili 10 Mar '17

10 Mar '17

I'd like to check worldwide connectivity to my site. I create a new measurement via web-interface and add, say, 300 probes, expecting them to cover most world countries. However, looking at the map <https://atlas.ripe.net/measurements/7861872/?filter=#map> I notice that most are selected from Europe: there're two dozens in Netherlands (many with same ASNs), but only two in Australia, one in Japan and nothing in Brazil. Obviously, most ATLAS probes are from Europe, and selection algorithm does not take probe density into account. Wouldn't it be nice to have the following features in web-interface and API: * even distribution of probes by country or continent based on population, area, and other user-defined weight numbers; * avoiding probes with same ASNs ? I don't know how current algorithm works, but easiest modification would be two-step process: (1) randomly select country based on specified weights; (2) randomly select probe within country, avoiding earlier selected probes or ASNs and failing if none are left available; repeat from step 1 until necessary number of probes is selected. P.S. I tried to manually request 1 probe from each country, but stumbled on unrecognised country codes, countries with no probes etc. before even trying population-weighted distribution. Without direct access to probes database nice solution can be difficult to achieve via current API, although crude one looks possible. P.P.S. I understand this option will create more load on probes in less-covered countries, but since it's possible to limit selection to specific countries anyway this is hardly a strong argument against adding this feature. -- With Best Regards, Marat Khalili

3 5

Testing DNS-over-TLS support?
by Stephane Bortzmeyer 10 Mar '17

10 Mar '17

DNS-over-TLS (RFC 7858) is important for privacy but, today, few DNS resolvers support it. It would be interesting to measure if this is changing, but the probes do not seem to be able to query their resolver with TLS over port 853. (Also, I seem to remember that old probes do not have a full TLS implementation.) It is not just a matter of encrypting the data, it's also an authentication issue (Google Public DNS was already impersonated <http://bgpmon.net/turkey-hijacking-ip-addresses-for-popular-global-dns-prov…>) So, how about adding a 'use_tls': True after 'use_probe_resolver': True?

2 2

No data in Connection & Traffic graph
by Danny Horne 09 Mar '17

09 Mar '17

Hi all, Is anyone not seeing any data on the Connection & Traffic graph in the General tab on their probe's homepage? (My probe ID 31491) Regards Danny Horne

2 1