- ripe-atlas - mailman.ripe.net

Probe #32536 with incorrect location
by Ponikierski, Grzegorz 11 Jun '18

11 Jun '18

Hi! Probe #32536 according to Atlas is located in India but its description, ASN and traceroutes suggest that in fact it's located Slovakia. Please verify. Regards, Grzegorz

2 1

New on RIPE Labs: Sketching Connectivity Between Users
by Mirjam Kuehne 04 Jun '18

04 Jun '18

Dear colleagues, We've been looking at user-to-user connections, based on RIPE Atlas measurements and ISP market share estimates provided by the APNIC. Please see some interesting graphs and a more detailed description in this new article on RIPE Labs: https://labs.ripe.net/Members/emileaben/sketching-connectivity-between-users Kind regards, Mirjam Kühne RIPE NCC

2 3

CLI
by Milad Afshari 03 Jun '18

03 Jun '18

Hi all, It's more than a month that I have a lot of issues with running measurements through CLI here from IRAN, the measurements starts correctly but the results will not be displayed. Do you have any idea to fix this or anyone else have the same problem? Many thanks Milad Afshari

2 5

Probe name rules
by Daniel AJ Sokolov 03 Jun '18

03 Jun '18

Hello, I would like to suggest a naming convention for probes that excludes names referring to features or networks which are not present/supported. For example, I see a probe that contains in its name a large network, although the probe is actually connected to competitor networks. (I assume the probe's host changed their ISP and forgot to update the probe's name.) Such naming is misleading for Atlas users, but also opens a can of worms in relation to trade mark law. Similarly, a prove with "IPv6" in its name that doesn't support IPv6 could be confusing. BR Daniel AJ

2 1

Probe #595 invalid location
by Ponikierski, Grzegorz 27 May '18

27 May '18

Hi! I cannot open page for probe #595 (question is why, it's private?) but from what I see this probe is marked as US probe: [cid:image001.jpg@01D3F5BB.36A72710] But AS 29422 is Finish ISP and when you check traceroute from this probe you will see that's for sure it's more Finland than US. Traceroute: 595 ----------------- 1 - 192.168.0.254 NA None NA 1.614ms 2 - 83.150.126.202 29422 None NBLNETWORKS-AS Nebula Oy, FI 15.026ms 3 - 188.117.15.250 29422 rtr1-te4-3.lau.hel.fi.nblnet.com NBLNETWORKS-AS Nebula Oy, FI 14.762ms <- Finland 4 - 80.239.132.5 1299 hls-b2-link.telia.net TELIANET Telia Carrier, SE 15.005ms <- Finland 5 - 80.91.245.214 1299 s-bb4-link.telia.net TELIANET Telia Carrier, SE 22.251ms <- Sweden 6 - 80.91.249.219 1299 s-b5-link.telia.net TELIANET Telia Carrier, SE 21.888ms 7 - 62.115.36.166 1299 akamai-ic-310810-s-b5.c.telia.net TELIANET Telia Carrier, SE 22.332ms <- Sweden 8 - 23.216.52.2 21342 a23-216-52-2.deploy.static.akamaitechnologies.com AKAMAI-ASN2, US 22.111ms Can you double check location of this probe? Regards, Grzegorz

1 0

Aggregator for TXT record
by Ponikierski, Grzegorz 24 May '18

24 May '18

Hi! I wanted to use Aggregator feature for DNS measurement but looks like it doesn't work with TXT record. Anybody has experience with this feature? Does Aggregator support TXT record? Regards, Grzegorz

1 0

New on RIPE Labs: Update on the RIPE Atlas Anchor VM pilot
by Alun Davies 14 May '18

14 May '18

Dear colleagues, We recently published an update on our pilot programme to assess the feasibility of introducing virtual machines to the pool of RIPE Atlas anchors. Read all about it in this RIPE Labs article from Robert Kisteleki: https://labs.ripe.net/Members/kistel/update-on-the-ripe-atlas-anchor-vm-pil… <https://labs.ripe.net/Members/kistel/update-on-the-ripe-atlas-anchor-vm-pil…> Best regards, Alun Davies RIPE NCC

1 0

Probe #33346 invalid location
by Ponikierski, Grzegorz 11 May '18

11 May '18

Hi! Found another probe assigned to incorrect country: https://atlas.ripe.net/probes/33346/#!tab-network Probe is located in Hong Kong but Atlas things it's China ;) Can you fix it? Regards, Grzegorz

1 0

Atlas #50012 handed over..
by Geert Jan de Groot 09 May '18

09 May '18

Hi, Lia just handed over probe 50012 (that's the new hardware version), and I plugged it into the AIS/AfriNIC network here in Dakar. Can you please make this probe "mine" so I can administer it? For the next few days, will try a few things (and please do so yourself!) My existing probe is 16233. Currently it is powered through the USB port of another device, I will try PoE later (it will switch to 100 mbit then). Currently it seems to do 1gbit. Will make notes and share with you. GJ

2 1

Probe #27786 invalid location
by Ponikierski, Grzegorz 07 May '18

07 May '18

Hi RIPE team! Probe #27786 is located UK but Atlas see it as US probe. It make measurements incorrect. Can you verify it? Regards, Grzegorz

2 1

Firmware version 4660
by BELLAFKIH hayat 07 May '18

07 May '18

Dear Atlas users I am using data collected by RIPE Atlas probes, I found data with a firmware *4660*, but I can't find definition of the structure related to this firmware here <https://atlas.ripe.net/docs/data_struct/> . Any help? Regards *Hayat BELLAFKIH*

2 1

Minor change in the API Participation Requests endpoint
by Agustin Formoso 03 May '18

03 May '18

Dear Atlas users, We're planning to roll-out a minor change in the API Participation Requests endpoint. We'll be changing the response that gets sent out when a Participation Request is submitted. Although minor, the change may break your code if you are making use of the response. Current response example: [35878] Future response example after roll-out: { 'request_ids': [35878] } We plan to put this change into production two weeks from now. For those who don't know what Participation Requests are, they allow you to add or remove probes from a pre-existing measurement. You can find more information in https://atlas.ripe.net/docs/api/v2/manual/participation_requests.html Regards — Agustín Formoso RIPE NCC

1 1

RIPE Atlas probe status issues
by Chris Amin 26 Apr '18

26 Apr '18

Dear RIPE Atlas users, There were various issues relating to the recorded status of RIPE Atlas probes over the weekend. This was brought to our attention by internal monitoring and information provided by users on the mailing list. Throughout this period most probes did actually remain connected to controllers, and measurement results were collected as normal. The side effects included: * the number of probes reported as connected by the system was lower than it should have been * the status (connected/disconnected) of many probes was incorrect * new measurements took longer than usual to start * fewer probes than usual were available for new measurements, leading in some cases to “no suitable” probes messages when trying to schedule new measurements * various system tags were incorrectly applied, including many probes being marked as having USB problems when this was not the case * temporary discrepancies with crediting/debiting of RIPE Atlas credits for the connected time of probes The issues were caused by a bug fix deployment at Friday 9AM UTC where a package was accidentally downgraded causing a regression to an old bug in the task handling of the central system. This bug caused a backlog of messages to build, slowing down or stopping the registering of various status messages in the system. Problems built up gradually as the backlog increased, until the root cause was identified on Sunday morning. The issue was then fixed and the system stabilized completely by about 10AM UTC. We have identified procedural and technical solutions that will stop this problem happening again, and are looking at ways to improve our monitoring of these kinds of issues. We apologise for any inconvenience or confusion caused by this event and would like to thank all of you who took the time to notify us of what you were seeing. Kind regards, Chris Amin RIPE NCC

2 1

Hidden measurements
by Marty Strong 25 Apr '18

25 Apr '18

Does anybody else find that measurements you’ve marked as hidden by clicking on the eye next to it disappear as expected, but don’t show up on the hidden tab (https://atlas.ripe.net/measurements/?page=1#tab-hidden)? Regards, Marty Strong -------------------------------------- Cloudflare - AS13335 Network Engineer marty(a)cloudflare.com +44 7584 906 055 smartflare (Skype) https://www.peeringdb.com/asn/13335

2 9

measurements "Forbidden"
by Marc Anthony Warrior 25 Apr '18

25 Apr '18

All of my RIPE Atlas measurement requests (pings in this case) are suddenly failing with a status "title" field value "Forbidden". Why is this happening?

4 6

paris traceroute output
by Radim Hrazdil 23 Apr '18

23 Apr '18

Hello all! I'm struggling to understand how is the number of paris variations reflected in the merasurement output. If I run paris-traceroute on my machine, the output of a single hop looks something like this: 6 P(16, 16) HOSTNAME (IP):0,1,2,3,4,9,10 4.534/6.072/15.130/2.957 ms HOSTNAME (IP):5,6,7,8 7.641/10.282/13.119/1.965 ms What I'm reffering to is this part: (IP):0,1,2,3,4,9,10, which says which probe packets 'visited' this particular router. I don't understand, how is this reflected in the measurement output. I have never encountered situaton in which 'from' fields within one hop would differ. This would suggest that no load balancing has been encountered, but that seems unlikely to me. Thanks for any replies, Radim Sent via RIPE Forum -- https://www.ripe.net/participate/mail/forum

1 0

dnssec validating system tag?
by Tapio Sokura 23 Apr '18

23 Apr '18

Hello, I was looking at the probe system tags at https://atlas.ripe.net/docs/probe-tags/ when dnssec validating resolvers came to mind. Has there been thoughts about making the probes do dnssec resolver statistics gathering? I.e. how many / which probes are configured with dns resolvers that do / don't do dnssec validation? Tapio

2 1

TLS error when the certificate is expired?
by Stephane Bortzmeyer 23 Apr '18

23 Apr '18

I'm reasonably certain that it has been possible to use 'sslcert' measurements even when the certificate is expired. Today, I try to use 'sslcert' with trigger-happy.eu and it fails: "alert": { "description": 40, "level": 2 }, And no certificate in the JSON output (this is measurement #12166428) 40 is the very general "handshake failure" of TLS. <https://www.iana.org/assignments/tls-parameters/tls-parameters.xhtml#tls-pa…> Was there a change in Atlas recently? The TLS server does reply: % gnutls-cli trigger-happy.eu Processed 167 CA certificate(s). Resolving 'trigger-happy.eu:443'... Connecting to '51.254.210.94:443'... - Certificate type: X.509 - Got a certificate list of 2 certificates. - Certificate[0] info: - subject `CN=trigger-happy.eu', issuer `CN=Let's Encrypt Authority X3,O=Let's Encrypt,C=US', serial 0x0359a66c5eb5da799afe079f87416f8d9641, RSA key 2048 bits, signed using RSA-SHA256, activated `2018-01-13 10:46:26 UTC', expires `2018-04-13 10:46:26 UTC', key-ID `sha256:8216c7a7f221f3efcf7e7c3eb1760275d6ebf38d153b74992ee7864147b54435' Public Key ID: sha1:668c4506a393d9bb633590b68c05d878734d7ffe sha256:8216c7a7f221f3efcf7e7c3eb1760275d6ebf38d153b74992ee7864147b54435 Public key's random art: +--[ RSA 2048]----+ | +. o++ | | o +*.=.. | | .=o* . . . | | * B o | | . = S . | | = . . | | + E | | . . | | | +-----------------+ - Certificate[1] info: - subject `CN=Let's Encrypt Authority X3,O=Let's Encrypt,C=US', issuer `CN=DST Root CA X3,O=Digital Signature Trust Co.', serial 0x0a0141420000015385736a0b85eca708, RSA key 2048 bits, signed using RSA-SHA256, activated `2016-03-17 16:40:46 UTC', expires `2021-03-17 16:40:46 UTC', key-ID `sha256:60b87575447dcba2a36b7d11ac09fb24a9db406fee12d2cc90180517616e8a18' - Status: The certificate is NOT trusted. The certificate chain uses expired certificate. *** PKI verification of server certificate failed... *** Fatal error: Error in the certificate. *** handshake has failed: Error in the certificate.

2 3

18774 is abandoned definitively ?
by Freddy BULOW 23 Apr '18

23 Apr '18

Hello, Is the status abandoned and definitive, or will it return to status online at its reconnection? If the usb key is new so with a FAT32 partition, the probe will do the necessary to restore the usb key? Thanks for your help. Sent via RIPE Forum -- https://www.ripe.net/participate/mail/forum

2 1

Request to RIPE Atlas probe hosts in Russia
by Roman Mamedov 23 Apr '18

23 Apr '18

Hello, Given the recent censorship events in Russia [1], some start using the Atlas probes to measure the impact of Roskomnadzor's imposed subnet and IP filtering on end users. For that to be as precise as possible, can you please ensure that your Atlas probe is plugged into the same network as your customers, i.e. subject to all the same filtering and blocking that the customers experience. (I guess this might not be the case if you simply plug it in into some switch next to your server infrastructure, which may be not going through the filters.) Thanks! [1] https://usher2.club/en/ -- With respect, Roman

1 0

Re: [atlas] Probe claimed to be offline
by Andre Heinrichs 22 Apr '18

22 Apr '18

Hi again, I'll add another weird experience from just now. When I last looked at the probe website it claimed the probe had been offline for over 1 day. But just half an hour ago when I looked the website said the probe had been online for 1day 6 hours (which is also not right seing how I've rebooted everything here less than 24 hours ago. And to add even more weirdness just as the hour switched I got the mail that my probe had been disconnected for more than 30 minutes. So right now the probe is offline for 13 hours and 41 minutes. So, basically there's something weird going on inside the Atlas system. Hopefully someone can correct whatever is causing it soon. TIA, Andre. Totally not keeping on refreshing the probe website.

1 0

Probe claimed to be offline
by Andre Heinrichs 22 Apr '18

22 Apr '18

Hi, my probe #29384 is reported as offline since the last network reconnect last night. According to the probe LEDs all looks okay (nothing is blinking, in the order of the FAQ they are On, off, on, on, on). But the website reports the probe as offline. Just the data plot ("Connection & Traffic") shows that the probe sends something out. I've already tried several reboots, did the USB reinitialization (twice, I tried a different USB storage as well) and I've also rebooted my FritzBox. All to no success. BTW: I've not been seeing SOS requests since I last reinitialized the USB in January when the probe was reported as offline as well. At least the USB-less boot showed up there. Is anyone else seeing this kind of problem? Is it a known problem somewhere? Or is there something else I could still try? TIA, Andre.

5 4

Re: [atlas] Paris-traceroute variations
by Radim Hrazdil 21 Apr '18

21 Apr '18

Hello all! I'm struggling to understand how is the number of paris variations reflected in the merasurement output. If I run paris-traceroute on my machine, the output of a single hop looks something like this: 6 P(16, 16) HOSTNAME (IP):0,1,2,3,4,9,10 4.534/6.072/15.130/2.957 ms HOSTNAME (IP):5,6,7,8 7.641/10.282/13.119/1.965 ms What I'm reffering to is this part: (IP):0,1,2,3,4,9,10, which says which probe packets 'visited' this particular router. I don't understand, how is this reflected in the measurement output. Moreover, I have never encountered situaton in which 'from' fields within one hop would differ. This would suggest that no load balancing has been encountered, but that seems unlikely to me. Thanks for any replies, Radim Sent via RIPE Forum -- https://www.ripe.net/participate/mail/forum

1 0

No suitable probes error, and inconsistency between results and measurement status
by Vasileios Giotsas 20 Apr '18

20 Apr '18

Hi all, I have a number of traceroute measurements that end-up with status "No suitable probes". The documentation explains that this error is quite rare, the quote below is from https://atlas.ripe.net/docs/udm/ "No suitable probes: The measurement cannot currently be executed as defined due to a lack of available probes. This may be because you asked to use probes that don't exist (for example, probes in an AS in which there are no probes) or because all of the probes you requested were too busy to take on new jobs. This latter scenario is very rare however." In my case happens in all of my latest measurement request that ask for different probes. It also happens when I use the wizard in the web interface which selects the probes automatically. Even weirder, some of these measurements appear to have been completed when I check the API. For instance, measurement 12244352 has status 6 (No suitable probes), and the web interface doesn't show any results. But the API endpoint shows that it has been executed and returned results: https://atlas.ripe.net/api/v2/measurements/12244352/ I'd appreciate some pointers on how to resolve this issue. Thanks, Vasileios

1 0

how to mark probe as dormant
by Randy Bush 18 Apr '18

18 Apr '18

i have a probe, 2283, which has unplugged from its old home and is in suspended animation in a suitcase until it reaches its new home in a month or two. the location map will not let me pur it in the middle of the pacific. and i can not see how to mark it as dormant/down. clue bat please. randy

4 7

New on RIPE Labs: Creating One-off Measurements with Blaeu, by Stéphane Bortzmeyer
by Vesna Manojlovic 17 Apr '18

17 Apr '18

Dear colleagues, Yesterday we published an article by Stéphane Bortzmeyer, where he presents Blaeu, a set of tools to create one-off measurements, mostly to debug temporary issues. Please find more details on RIPE Labs: https://labs.ripe.net/Members/stephane_bortzmeyer/creating-ripe-atlas-one-o… Kind regards, Vesna Manojlovic RIPE NCC

1 0

New on RIPE Labs: RIPE Atlas Measurement Tagging
by Mirjam Kuehne 12 Apr '18

12 Apr '18

Dear colleagues, The new RIPE Atlas measurement tagging feature is now available. Please find more details in this new RIPE Labs article: https://labs.ripe.net/Members/chris_amin/ripe-atlas-measurement-tagging Kind regards, Mirjam Kühne RIPE NCC

1 0

Join Network Operators' Tools Hackathon 23-24. June 2018 in Dublin; organised by: iNOG & RIPE NCC
by Vesna Manojlovic 10 Apr '18

10 Apr '18

Dear colleagues, The seventh RIPE NCC hackathon will take place on Saturday and Sunday, 23-24 June 2018 in Dublin -- co-hosted by iNOG (Irish Network Operators Group), whose 16th edition is happening on Thursday, 21st June. The topic this time is: tools for network operators. Find out more in this RIPE Labs article: https://labs.ripe.net/Members/becha/join-network-operators-tools-hackathon RIPE NCC hackathons are cooperative, and all source code developed during the event will be publicly licensed and available on GitHub, and will be free for the entire community to use. -------------------- How to Apply -------------------- Interested? Learn more and apply online today! https://www.ripe.net/participate/forms/apply/dublin-hackathon/ *The first application deadline is 1st May* We look forward to seeing you there! Regards, Vesna Manojlovic Community Builder RIPE NCC

1 0

Result streaming lacking results
by Tim Wattenberg 14 Mar '18

14 Mar '18

Hi everyone, I'm working on a project where I create a measurement via API and immediately subscribe to the result stream as well as the metadata stream ( https://atlas.ripe.net/docs/api/v2/manual/measurements/result-streaming.html ). socket.emit("atlas_subscribe", {stream_type: "result", msm: mid, sendBacklog: true}); socket.emit("atlas_subscribe", {stream_type: "metadata", msm: mid}); Now even with (and also without) the sendBacklog option enabled, I rarely get even close to receive all results (the measurement produces max. 10 in total, I received max. 4-5, often only one or even none). Same goes for metadata, where I sometimes get the action: creation event, but never a notification when the measurement is stopped. Another question in this context: When does a one-off measurement gets stopped? I also subscribed to (dis)connect, atlas_error and atlas_subscribed but they give no hint what could be going wrong. I also tried the replay feature, which did not work at all for me either: socket.emit("atlas_subscribe", {stream_type: "result", msm: mid, startTime: <Time of creation>}); What am I doing wrong? Thanks, Tim Tim Wattenberg mail(a)timwattenberg.de +49 1578 8248731

2 1

API Keys problem?
by Daniel Ankers 09 Mar '18

09 Mar '18

Hi, Has there been a change in the way that API keys work for the measurement results API? I've got an API key which is granted permission to get results from a non-public measurement. When I do: curl -H "Authorization: Key $KEY" " https://atlas.ripe.net/api/v2/measurements/$MEASUREMENT/results/?start= 1520510400" (Replacing $KEY with the key and $MEASUREMENT with the measurement ID) I get: {"error":{"status":400,"errors":[{"source":{"pointer":""},"detail":"Your keys has no grants"}],"code":102,"detail":"There was a problem with your request","title":"Bad Request"}} This was previously working, but I'm not sure exactly when it stopped. I've checked that getting the data through my browser works while I'm logged into the site, and that if I request https://atlas.ripe.net/api/v2/measurements/$MEASUREMENT/latest using the API key I get data returned. Regards, Dan

4 5

New on RIPE Labs: Announcing Daily RIPE Atlas Data Archives
by Mirjam Kuehne 02 Mar '18

02 Mar '18

Dear colleagues, In this article we present a new way to access the dataset on the RIPE Atlas platform. Instead of fetching individual results from measurements using the available APIs, you can now download files containing public measurements for a given day. Please find more details on RIPE Labs: https://labs.ripe.net/Members/petros_gigis/announcing-daily-ripe-atlas-data… Kind regards, Mirjam Kühne RIPE NCC

9 12

New on RIPE Labs: OpenIPmap - A Collaborative Approach to Mapping Internet Infrastructure
by Mirjam Kuehne 14 Feb '18

14 Feb '18

Dear colleagues, OpenIPmap, the RIPE NCC’s tool for geolocating core Internet infrastructure, has undergone a full architectural overhaul. With a new set of APIs and interfaces designed to cater to the needs of all users, the system integrates various methods for estimating the geographical locations of IXPs, core routers and other components of Internet infrastructure. In this, the first of two RIPE Labs articles on the topic, we look at the evolution of OpenIPmap from its inception to today: https://labs.ripe.net/Members/jasper_den_hertog/openipmap-a-collaborative-a… Kind regards, Mirjam Kühne RIPE NCC

1 0

Re: [atlas] multiple measurements failed on probe 15861
by ripe＠brite.cz 12 Feb '18

12 Feb '18

Please disregard. The measurements eventually delivered at 2018-02-10, while measurement was created and all other probes delivered their results at 2018-02-07. Thats weird, but at eventually it works. Thank you Jiri ______________________________________________________________ > Od: <ripe(a)brite.cz> > Komu: <ripe-atlas(a)ripe.net> > Datum: 09.02.2018 16:42 > Předmět: multiple measurements failed on probe 15861 > > >Hi team, >it seems traceroute measurements fail on Probe 15861: > >-following measurements created only for Probe 15861: >https://atlas.ripe.net/measurements/11204846/ >https://atlas.ripe.net/measurements/11204847/ >both ended up with "Failed" result > > >-following measurements contain multiple probes together with Probe 15861, and whereas other probes give results as expected, for this probe the result show "No recent report available": >https://atlas.ripe.net/measurements/11194845/ >https://atlas.ripe.net/measurements/11194846/ > >Built-in measurements look fine though. > >Any idea? Am I doing something wrong? >The probe is located at my home, connected to switch where all other devices work fine. > >Thank you > >Jiri > >

1 0

multiple measurements failed on probe 15861
by ripe＠brite.cz 09 Feb '18

09 Feb '18

Hi team, it seems traceroute measurements fail on Probe 15861: -following measurements created only for Probe 15861: https://atlas.ripe.net/measurements/11204846/ https://atlas.ripe.net/measurements/11204847/ both ended up with "Failed" result -following measurements contain multiple probes together with Probe 15861, and whereas other probes give results as expected, for this probe the result show "No recent report available": https://atlas.ripe.net/measurements/11194845/ https://atlas.ripe.net/measurements/11194846/ Built-in measurements look fine though. Any idea? Am I doing something wrong? The probe is located at my home, connected to switch where all other devices work fine. Thank you Jiri

1 0

failing IPv6 ping to a.root-servers.net
by Wolfgang S Rupprecht 03 Feb '18

03 Feb '18

My probe #35105's builtin test "#2009 Ping to a.root-servers.net (2001:503:ba3e::2:30)" fail most of the time while IPv6 pings to other targets work just fine. From poking around other probes, this seems to be a common problem. I wonder if this is why my probe never keeps its "IPv6 Stable 1d" tag for long when it does eventually get it. The way I see it, that one failing test set puts the probe below the 95% working cutoff for IPv6. Are other people seeing the same failing ping6 to a.root-servers.net? 2018-01-25 12:33:27 UTC Probe auto-untagged Your probe #35105 was automatically untagged as "system: IPv6 Stable 1d" 2018-01-25 08:35:56 UTC Probe auto-tagged Your probe #35105 was automatically tagged as "system: IPv6 Stable 1d" -wolfgang

2 1

False positives on SSL check?
by Ruben Herold 02 Feb '18

02 Feb '18

hi, I tried to monitor on of our services running on https://login.afterbuy.de. I configured an SSL check like (Meassure ID #11090260). All probes response with: Error: timeout reading hello But the service is online and reachable. SSLabs SSL check confirmed this. So can someone explain what the error message will tell me? Thx Ruben Sent via RIPE Forum -- https://www.ripe.net/participate/mail/forum

2 3

tag "system: IPv6 Works"
by Wolfgang S Rupprecht 29 Jan '18

29 Jan '18

I just joined the RIPE-Atlas fold with probe #35105 and am still learning the ropes. My public-facing internet servers are all IPv6-only. That means that the only meaningful measurements of my systems come from IPv6 capable probes. I was surprised to see that IPv4-only probes would be scheduled to send IPv6 pings, traceroutes, nslookups etc. Even when I added "system: IPv6 Works" to the include tags and "system: IPv6 Doesn't Work" to the exclude tags I still got some IPv4-only probes assigned. Are those tags for future use and not wired up yet? Are the IPv4-only probes I'm seeing in my test runs there because their status changed recently and previously they were IPv6 capable? -wolfgang

2 1

Connectivity Problems in China
by Klaus Darilion 27 Jan '18

27 Jan '18

Hi! I have probe #248 which was working fine for long time. Now I sent it to a friend in China. He connected it to his home DSL account but the probe is still disconnected. Are you aware of any firewall problems for probes in China? Should the be able to connect on a normal residental Internet access? Where does the probes tries to connect? (Hostname, IP) so I can try to telnet the IP:port from a normal PC. Thanks Klaus

2 1

New on RIPE Labs: Measurements as the Key to Transparency
by Mirjam Kuehne 25 Jan '18

25 Jan '18

Dear colleagues, In this new article on RIPE Labs Alexander Azimov describes how they built a tool to visualise network latency measured with RIPE Atlas. https://labs.ripe.net/Members/alexander_azimov/measurements-as-the-key-to-t… Kind regards, Mirjam Kühne RIPE NCC

1 0

Probe shown as offline although LEDs appear online
by Andre Heinrichs 25 Jan '18

25 Jan '18

Hi, My Probe #29384 has started being reported as offline although the LEDs show no problem. I’ve just tried switching to another USB stick without apparent success. The weird part is that the probe seems to not send any SOS requests as soon as it started running off the USB. I’m guessing that makes it offline. If I’m interpreting the connection & traffic graph correctly the probe is still able to return results. Any advice what I could do now would be appreciated. TIA, Andre Heinrichs

1 1

Query
by Informática IPYS 23 Jan '18

23 Jan '18

Hi, I'm Francisco Colmenares from IPYS Venezuela. I am writing to you because I have a conuslta. After having registered on the RIPE ATLAS page, connect the RIPE to the network, however when I search for the ID in the search engine that has the web page it gives me the ERROR: 101: no entries found. Is there a step I'm missing? Greetings. -- Francisco Colmenares Desarrollo web y Soporte técnico. IPYS Venezuela 0426-1991873

1 0

HTTP server configuration fix deployed to v3 anchors
by Stephen D. Strowes 22 Jan '18

22 Jan '18

Hi, Recently we identified a web server misconfiguration on our v3 anchors, such that those anchors would not respond as expected to requests with their IP literal in the URL. Requests to their FQDN worked as expected. In other words: * http://nl-ams-as3333-3.anchors.atlas.ripe.net:80/ would respond as expected, but * http://[2001:67c:2e8:3::c100:a4]:80/ would respond with a 404 status code. The configuration was fixed and deployed by around 0900UTC on 16 January, 2018. V3 anchors now respond correctly to requests issued with their IP literal in the URL. This affected HTTP measurements to v3 anchors as follows: * Before the fix was deployed, HTTP measurements to a v3 anchor with 'Resolve on probe' set to false will have used the IP literal, and thus logged a 404 status code. * HTTP measurements as above that were running when the fix was deployed will have started returning correct results part-way through their run. If the measurement is ongoing, no other action needs to be taken. * HTTP measurements with 'Resolve on probe' set to true always operated as expected. Cheers, Stephen Strowes RIPE NCC

1 0

Minor changes in the credits transactions API endpoint
by Viktor Naumov 17 Jan '18

17 Jan '18

Dear colleagues, We made some changes to the credits transactions API. The changes relate to the use of another storage back-end. * Transaction IDs are no longer used to retrieve the data. * There is no detail transaction endpoint anymore, all transactions are served as paged lists. * The main transaction endpoint remains /api/v2/credits/transactions/ Deprecated endpoints are as follows: * /api/v2/credits/transactions/<transaction_id> * /api/v2/credits/transactions/admin/<transaction_id> * /api/v2/credits/transactions/measurement/<transaction_id> * /api/v2/credits/transactions/probe/<transaction_id> The transactions endpoint reference is accessible at: https://atlas.ripe.net/docs/api/v2/reference/ Best regards, Viktor Naumov RIPE NCC

1 0

Probe and firewall settings?
by Tim Chown 15 Jan '18

15 Jan '18

Hi, At https://atlas.ripe.net/about/faq/#so-which-services-do-i-need-for-my-probe-… it says "The absolute minimum set is DHCP, DNS and outgoing TCP port 443 (HTTPS) in order to allow the probe to connect to the network. However, this in itself is not enough to do measurements, which is the entire focus of RIPE Atlas, so you should also allow ICMP, UDP (DNS + traceroute), TCP for traceroute and HTTP(S)." What specific ports and protocols are required for routine operation and for inbound or outbound measurements to be configured? I think the above info could be a little more detailed (having had questions asked of me). Many thanks, Tim

2 2

beta status page vs. ipv6 only network
by Bjoern Buerger 15 Jan '18

15 Jan '18

Hi, One of our probes has a warning "IPv4 Doesn't Work Properly" on the beta Status Page, along with a "IPv4 doesn't work" Tag on the main page. While this is technically correct, the cause is simple and nothing is broken. We just removed IPv4 from that specific network segment (because it's not needed anymore). Is it possible to somehow tag the probe as "single stack on purpose" in the configuration page? Thanks in advance, Bjørn

3 2

#6262 Disconnectted
by Stanish Stanishev 12 Jan '18

12 Jan '18

Hello, Yesterday i got a notification that one of the our Anchors - #6262 has disconnected from Atlas. According to its Current Status info - DNS Problem Suspected. I see the anchor is configured to use the following DNS Resolvers - 8.8.8.8 and 2620:74:1b::1:1. The anchor responds to pings and is reachable from the world. Also the resolvers 8.8.8.8 are 2620:74:1b::1:1 reachable from the anchor's uplink router. So apart from checking the anchor's connectivity and DNS resolvers I don't have much left to do in order to get the anchor connected again. Has anyone faced this situation before ? Thanks Stanish Sent via RIPE Forum -- https://www.ripe.net/participate/mail/forum

3 2

Minor changes in the probe archive API
by Viktor Naumov 10 Jan '18

10 Jan '18

Dear colleagues, We made some changes to the probe archives API. The changes relate to the use of another storage back-end. In addition to the "date" URL argument, which returns the all probes dump for the given date, the new version enables ranges of dates to be specified for all or selected probes. The example below will return dumps for probes 1, 5, 81, 82, 83 for dates in the range [2018-01-03, 2018-01-06): https://atlas.ripe.net/api/v2/probes/archive?/api/v2/probes/archive?date__g… Best regards RIPE Atlas Team

1 1

RIPE Atlas CLI
by Milad Afshari 03 Jan '18

03 Jan '18

Hi Dear Colleagues; I hope you are doing well; I have an issue with creating a measurement using " --include-tag" option,As far as I check the syntax is correct but it doesn't work.Please let me know if you have any idea. cmd: *a) - ripe-atlas measure ping --from-country ir --target 79.127.127.1 --include-tag system-ipv4-works* *b) ripe-atlas measure ping --from-country ir --target 79.127.127.1 --include-tag=system-ipv4-works* Error: *ripe-atlas measure: error: argument --include-tag: "system-ipv4-works" does not appear to be valid.* Regards Milad

2 1

Probe didn't get static IP address
by Walid Ben Ali 29 Dec '17

29 Dec '17

Dear ripe Atlas support, My probe ID 26099<https://atlas.ripe.net/probes/26099/> didn't reconize the static IP adress. Knowing that it worked for days. Today I just tried to know if it is a network problem or a probe issu, I just conenct it into DHCP and the probe works., I also pluged my Laptop to the netwok with the static IP address (in order to know if it is a network issu) and also the network ork perfectly, I even surfed on the RIPE NCC web site without any pb. So please RIPE Atlas support, could you bring me some help? I returned back the probe to the nework, the static specified IP is kept, (with the DNS and submask and so on), but the probe didn't work. Looking for your support Many thanks

1 0

New on RIPE Labs: Plan of Action for RIPE Atlas Anchor VMs
by Mirjam Kuehne 27 Dec '17

27 Dec '17

Dear colleagues, Members of the RIPE Atlas community have asked us to implement RIPE Atlas vantage points as Virtual Machines (VMs). In order to address these requests, we came up with a plan of action: https://labs.ripe.net/Members/kistel/plan-of-action-for-ripe-atlas-anchor-v… Kind regards, Mirjam Kühne RIPE NCC

4 3