- ripe-atlas - mailman.ripe.net

X.509 certificate monitoring
by Stephane Bortzmeyer 25 Aug '15

25 Aug '15

I do not find a lot of examples of X.509 certificate retrieving and analysis? I just committed <https://github.com/RIPE-Atlas-Community/ripe-atlas-community-contrib/blob/m…> which is useful for me when watching certificate expiration for anycasted sites (where the cert retrieved depends on the probe). Any other examples? And by the way, do not hesitate to submit your scripts to <https://github.com/RIPE-Atlas-Community/ripe-atlas-community-contrib> (fork and pull request, or open an issue with the attached script).

1 0

Re: [atlas] Question about "location setting" of RIPE Atlas
by Tomáš Hetmer 23 Aug '15

23 Aug '15

Hi, I'd use the simplest logical interpretation and enter the actual physical location no matter if the actual interconnect is right there, 900 km away or transmitted from a satellite. Also, if you placed it to that location 900km away you wouldn't skew the results for your own town, but anyone measuring the latency there would see a +20ms difference from reality, so that doesn't improve anything. Many networks are large and complex, such as an ADSL for a whole country being connected to the net via a local MPLS network via a central point at one main location - should you use that one for all the probes in the country? Of course not, you enter wherever the endpoint is. If you'd like however, you can mention your specific configuration in the probe details. That's my personal view on this, others might differ. Regards Tomáš Hetmer 2015-08-22 23:42 GMT+02:00 Anurag Bhatia <me(a)anuragbhatia.com>: > I have been hosting one of RIPE probes and recently I have switched over my > ISP. > > > Basically my previous ISP provider was regular ISP network with full L3 PoPs > nearby but in my new setup I have got a point to point to a city 900km away > and getting IP transit over there. > > > Now under such case, I am "technically" customer of that network. Should I > still keep my location as I have current one or better update it to that new > location 900km away? > > > The latency of course is low (as it is provisioned on fiber and hence just > 20ms roundtrip) but I think it will confuse off stats if anyone considers to > use this probe for any data in my region. > > > What you all think? Can someone recommend on correct location? > > > > Thanks. > > -- > > > Anurag Bhatia > anuragbhatia.com > > > PGP Key Fingerprint: 3115 677D 2E94 B696 651B 870C C06D D524 245E 58E2

1 0

Afilias, Los Angeles, CA, United States has joined RIPE Atlas anchors
by Eamonn Lane 21 Aug '15

21 Aug '15

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-lax-as63403 and is hosted by Los Angeles, CA, 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, RIPE Atlas Team RIPE NCC atlas(a)ripe.net

1 0

: Afilias, Ashburn, VA 20147, United States has joined RIPE Atlas anchors
by Eamonn Lane 21 Aug '15

21 Aug '15

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-qas-as393246 and is hosted by Afilias, Ashburn, VA 20147, 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, RIPE Atlas Team RIPE NCC atlas(a)ripe.net

1 0

Afilias (US, Ashburn and Los Angeles) have joined RIPE Atlas anchors
by Michela Galante 20 Aug '15

20 Aug '15

Dear RIPE Atlas users, We're happy to announce that two more RIPE Atlas anchors have joined the network and are now available as targets for probe hosts conducting their own user-defined measurements. The new anchors, both hosted by Afilias in United States, are: us-qas-as393246, in Ashburn (Virginia) us-lax-as63403, in Los Angeles (California) Congratulations to Afilias for their second and third anchor online! 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/ Thank you for participating in RIPE Atlas! Kind regards, RIPE Atlas Team RIPE NCC atlas(a)ripe.net

1 0

Case sensitive DNS queries from the probe
by Yang Yu 19 Aug '15

19 Aug '15

Hello, Looking through DNS queries log I saw tons of queries from the probe for case sensitive names. Can someone please enlighten me what the possible use cases are? query: wWw.FacebOOK.COm IN A query: wWW.Wikia.COM IN A query: WwW.wIkIA.cOM IN A query: POOl.NTP.ORg query: Www.wikiA.CoM IN A query: wWW.FacebOoK.COM IN A query: wWw.faCeBOoK.cOM IN A Yang

7 15

Excluding probes by user defined tag not working
by Yang Yu 14 Aug '15

14 Aug '15

Hello, When I use New Set - wizard to select probes, the exclusion by tag does not work with user tags. Even though the user tag was recognized (I chose it from the drop down menu), the particular probe was still selected. For example, I excluded user tag SDFJLKFWEO from measurement 2312281, but probe 10240 was still selected. Thanks. Yang

3 2

Promote the use of IRC
by Daniel Baeza (Red y Sistemas TVT) 14 Aug '15

14 Aug '15

Hi all, Yesterday, I've started a discussion in the member list about promoting the use of IRC instead of Mail List for some kind of discussions, chit chat, etc. Not much members answered, but all who did said yes. The goal is to have, at least, one channel per mail list, but not limited to only that. For this list, an #atlas channel will be created and administrated by the WG Chairs. We want to use the actual RIPE IRC Server plus Network Services and some more irc servers linked to the Ripe one. What do you think? Regards, --Daniel

8 8

one-off UDMs more expensive?
by Paul Vlaar 10 Aug '15

10 Aug '15

As I go through the web interface to setup a UDM I notice the following: For the same DNS measurement, when I specify an interval of 24 hours between samples, the total daily cost comes to 10. When however I specify this to be a one-off sample, the cost then doubles to 20. This doesn't seem to make sense to me. Is there a special reason for one-off measurements to be twice as expensive? ~paul

2 2

selecting probes based on place/city?
by Paul Vlaar 08 Aug '15

08 Aug '15

Hi all, I was wondering if anyone managed to come up with a method of getting a probe selection via the API that is based on city. The web interface allows this, by searching for "place", which is subsequently handled by the Google Maps API (I think), and which then comes back with a number of probes on the map, in that given place. However I need this in the API, which only allows to select probes based on "area, country, prefix, asn". What I'm currently trying to come up with is a way to map, more or less, onto the list of ICANN specified probing locations for their DNS tests. This list is published here: https://tld-monitor.icann.org/nodes.csv I've been trying to go by the ASNs that the listed locations have their IP space in, but that frequently gives me a negative result (no probes present). The same for the prefixes themselves, of course. And just going by the enclosing country code is fine for a small place like Luxembourg, but not for a big country like Canada. So if anyone has any ideas on how to achieve this in a dynamic way (so as not to have to manually build and maintain a list of probes), I'd be very interested in hearing about that. Thank you, Paul Vlaar

4 6