- ripe-atlas - mailman.ripe.net

Scheduled work on RIPE Atlas
by Robert Kisteleki 18 Jul '19

18 Jul '19

Dear RIPE Atlas users, We have planned maintenance on the main RIPE Atlas backend database tomorrow (Tuesday, 16 July) starting at 08:00 UTC, 10:00 Amsterdam local time. We expect complete unavailability of the service for a short while and further intermittent delays during the day. During this time the website (UI and APIs) will not be responding (properly). This also means that requests for new measurements will be denied or delayed. Data from existing measurements will still be collected normally, though access to them will be impacted. Our apologies for the inconvenience. Regards, Robert Kisteleki

3 4

Re: [atlas] how to earn credits com236.294.813
by kiran.gunana＠colruytgroup.com 11 Jul '19

11 Jul '19

Hello Johan, My probe ID is 32256, It is registered and reachable from last 3 weeks, can you please check if I still need to do something to earn my credits. rg, kiran. ----- Original Message: com236.291.250 --------------------------------- From: Johan ter Beest (jterbeest(a)ripe.net) To: kiran.gunana(a)colruytgroup.com Copy: ripe-atlas(a)ripe.net Subject: Re: [atlas] how to earn credits com236.259.148 Date: 11 July 2019 (12:07) Hi Kiran, You earn credits for the uptime of a probe and the delivered results for measurements that other hosts run towards your probe. Everything is explained here: https://atlas.ripe.net/docs/credits/ If your probe is not earning you any credits then there are two possible reasons: - your probe is not connected - you have not registered your probe so we don’t know who to give the credits to. I don’t know your probe ID so I. Cannot check but it’s most likely that it’s not registered. You can do that here: https://atlas.ripe.net/register/ If you send me a private email with your probe ID, I will give you the credits you should have earned in the last three weeks. Kind regards, Johan ter Beest RIPE Atlas. Team On 11 Jul 2019, at 09:10, kiran.gunana(a)colruytgroup.com wrote: Hello Michael, Thanks alot for the good gesture, me too got some good number of credits for now however just wondering after 3 months I will loose them all if I keep doing the same measurments. So looking for a way to earn some credits. rg, kiran ----- Original Message: com236.253.880 --------------------------------- From: Michael J. Oghia (mike.oghia(a)gmail.com) To: kiran.gunana(a)colruytgroup.com Copy: ripe-atlas(a)ripe.net Subject: Re: [atlas] how to earn credits com236.252.126 Date: 11 July 2019 (08:34) Can we just transfer you some credits? Most of us have a massive surplus. Let us know your preferred email address. Best, -Michael On Thu, Jul 11, 2019, 8:16 AM <kiran.gunana(a)colruytgroup.com> wrote: Hello, I am running my probe since 3 weeks and I spent almost 1milion credits for measuring some metrics, however I am not able to earn any credits. Can some give me the steps to enable me earning some credits as well. rg, kiran. Dit bericht is onderworpen aan de voorwaarden beschikbaar op onze website Ce message est soumis aux conditions disponibles sur notre site web This message is subject to the terms and conditions available on our website Dit bericht is onderworpen aan de voorwaarden beschikbaar op onze website Ce message est soumis aux conditions disponibles sur notre site web This message is subject to the terms and conditions available on our website Dit bericht is onderworpen aan de voorwaarden beschikbaar op onze website Ce message est soumis aux conditions disponibles sur notre site web This message is subject to the terms and conditions available on our website

1 0

Re: [atlas] how to earn credits com236.259.148
by kiran.gunana＠colruytgroup.com 11 Jul '19

11 Jul '19

Hello Michael, Thanks alot for the good gesture, me too got some good number of credits for now however just wondering after 3 months I will loose them all if I keep doing the same measurments. So looking for a way to earn some credits. rg, kiran ----- Original Message: com236.253.880 --------------------------------- From: Michael J. Oghia (mike.oghia(a)gmail.com) To: kiran.gunana(a)colruytgroup.com Copy: ripe-atlas(a)ripe.net Subject: Re: [atlas] how to earn credits com236.252.126 Date: 11 July 2019 (08:34) Can we just transfer you some credits? Most of us have a massive surplus. Let us know your preferred email address. Best, -Michael On Thu, Jul 11, 2019, 8:16 AM <kiran.gunana(a)colruytgroup.com> wrote: Hello, I am running my probe since 3 weeks and I spent almost 1milion credits for measuring some metrics, however I am not able to earn any credits. Can some give me the steps to enable me earning some credits as well. rg, kiran. Dit bericht is onderworpen aan de voorwaarden beschikbaar op onze website Ce message est soumis aux conditions disponibles sur notre site web This message is subject to the terms and conditions available on our website Dit bericht is onderworpen aan de voorwaarden beschikbaar op onze website Ce message est soumis aux conditions disponibles sur notre site web This message is subject to the terms and conditions available on our website

3 2

how to earn credits com236.252.126
by kiran.gunana＠colruytgroup.com 11 Jul '19

11 Jul '19

Hello, I am running my probe since 3 weeks and I spent almost 1milion credits for measuring some metrics, however I am not able to earn any credits. Can some give me the steps to enable me earning some credits as well. rg, kiran. Dit bericht is onderworpen aan de voorwaarden beschikbaar op onze website Ce message est soumis aux conditions disponibles sur notre site web This message is subject to the terms and conditions available on our website

2 1

Re: [atlas] DNS RTT over TCP: twice as long than UDP?
by Ponikierski, Grzegorz 11 Jul '19

11 Jul '19

Just to confirm I verified what exactly dig measures. For example, this dig takes 8ms (which is always rounded): [gponikie@krk-mptoy atlas_day68_step1]$ dig +tcp example.com @1.1.1.1 ; <<>> DiG 9.14.3 <<>> +tcp example.com @1.1.1.1 ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 14416 ;; flags: qr rd ra ad; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 1452 ;; QUESTION SECTION: ;example.com. IN A ;; ANSWER SECTION: example.com. 5212 IN A 93.184.216.34 ;; Query time: 8 msec ;; SERVER: 1.1.1.1#53(1.1.1.1) ;; WHEN: Tue Jul 09 13:17:55 CEST 2019 ;; MSG SIZE rcvd: 56 If you check it with wireshark it looks like this: No. Time Source Destination Protocol Length Window size value Shift count Info 1 13:17:55.014898 192.168.1.83 1.1.1.1 TCP 78 65535 6 53593 → 53 [SYN] Seq=0 Win=65535 Len=0 MSS=1460 WS=64 TSval=676915370 TSecr=0 SACK_PERM=1 2 13:17:55.029784 1.1.1.1 192.168.1.83 TCP 74 29200 10 53 → 53593 [SYN, ACK] Seq=0 Ack=1 Win=29200 Len=0 MSS=1412 SACK_PERM=1 WS=1024 3 13:17:55.029883 192.168.1.83 1.1.1.1 TCP 54 4096 53593 → 53 [ACK] Seq=1 Ack=1 Win=262144 Len=0 4 13:17:55.030041 192.168.1.83 1.1.1.1 DNS 108 4096 Standard query 0x3850 A example.com OPT 5 13:17:55.038351 1.1.1.1 192.168.1.83 TCP 68 29 53 → 53593 [ACK] Seq=1 Ack=55 Win=29696 Len=0 6 13:17:55.038572 1.1.1.1 192.168.1.83 DNS 120 29 Standard query response 0x3850 A example.com A 93.184.216.34 OPT 7 13:17:55.038624 192.168.1.83 1.1.1.1 TCP 54 4095 53593 → 53 [ACK] Seq=55 Ack=59 Win=262080 Len=0 8 13:17:55.039580 192.168.1.83 1.1.1.1 TCP 54 4096 53593 → 53 [FIN, ACK] Seq=55 Ack=59 Win=262144 Len=0 9 13:17:55.047201 1.1.1.1 192.168.1.83 TCP 68 29 53 → 53593 [FIN, ACK] Seq=59 Ack=56 Win=29696 Len=0 10 13:17:55.047273 192.168.1.83 1.1.1.1 TCP 54 4096 53593 → 53 [ACK] Seq=56 Ack=60 Win=262144 Len=0 From this traffic looks like dig measures time between packets 4 (DNS query) and 6 (DNS response) which is precisely 8.5ms and matches what dig shows. Including TCP handshake it takes 23.7ms, 2.8x longer which is expected . RTT can be measured on different layers for the same communication stream. In case of DNS over UDP we just ignores UDP overhead because it doesn't add any packets. With TCP additional packets are added which significantly increase time that end-user have to wait from first packet to get information that he/she needs. IMO RTT should always be measured from 1st packet to packet which has information that you have actual data. If we want to measure raw DNS performance without overhead then it must be explicitly market it measurement description. Regards, Grzegorz From: Giovane Moura <giovane.moura(a)sidn.nl> Date: Friday 2019-07-05 at 14:34 To: "ripe-atlas(a)ripe.net" <ripe-atlas(a)ripe.net> Subject: [atlas] DNS RTT over TCP: twice as long than UDP? Folks, This page at Atlas provides a great visualization on the RTT of DNS queries over TCP/UDP to the Root DNS servers: https://atlas.ripe.net/results/maps/root-server-performance/ We can see that the RTT of TCP queries is at least twice as long than UDP ones (which, according to the page " TCP is expected to be 2-3 times " longer. I cannot replicate these results in my setup, even in large scale from various vantage points: I always get very similar results for either TCP or UDP. Example: UDP: * $ dig example.nl @ns1.dns.nl Query time: 8 msec TCP: * $dig +tcp example.nl @ns1.dns.nl Query time: 9 msec I think there might be something with the definition of RTT. My hypothesis is that the field *rtt* on DNS queries on Atlas[1], for TCP, is, in fact, measuring 2 RTTs: the RTT of the TCP handshake, and the RTT of query/response itself. By definition, however, RTT is "the length of time it takes for a signal to be sent plus the length of time it takes for an acknowledgement of that signal to be received."[2]. So if DNS TCP measurements starts measuring from the SYN packet, that', in fact, be two RTTs. Is this the case with Atlas? I know it may sound a bit like nitpicking, but I just want to be sure of what's exactly being measured. thanks a lot, /giovane [1] https://atlas.ripe.net/docs/data_struct/#v4750_dns [2] https://en.wikipedia.org/wiki/Round-trip_delay_time

2 2

New on RIPE Labs: Internet Tools BoF Discovers Common Challenges for Network Operators
by Michela Galante 09 Jul '19

09 Jul '19

Dear colleagues, Here is a great summary provided by Sofia Silva Berenguer (APNIC) of the outcomes of the Internet Tools BoF organised at the recent LACNIC 31 meeting: https://labs.ripe.net/Members/sofia_silva_berenguer/internet-tools-bof-disc… Kind regards, Michela Galante RIPE NCC

1 0

DNS RTT over TCP: twice as long than UDP?
by Giovane Moura 05 Jul '19

05 Jul '19

Folks, This page at Atlas provides a great visualization on the RTT of DNS queries over TCP/UDP to the Root DNS servers: https://atlas.ripe.net/results/maps/root-server-performance/ We can see that the RTT of TCP queries is at least twice as long than UDP ones (which, according to the page " TCP is expected to be 2-3 times " longer. I cannot replicate these results in my setup, even in large scale from various vantage points: I always get very similar results for either TCP or UDP. Example: UDP: * $ dig example.nl @ns1.dns.nl Query time: 8 msec TCP: * $dig +tcp example.nl @ns1.dns.nl Query time: 9 msec I think there might be something with the definition of RTT. My hypothesis is that the field *rtt* on DNS queries on Atlas[1], for TCP, is, in fact, measuring 2 RTTs: the RTT of the TCP handshake, and the RTT of query/response itself. By definition, however, RTT is "the length of time it takes for a signal to be sent plus the length of time it takes for an acknowledgement of that signal to be received."[2]. So if DNS TCP measurements starts measuring from the SYN packet, that', in fact, be two RTTs. Is this the case with Atlas? I know it may sound a bit like nitpicking, but I just want to be sure of what's exactly being measured. thanks a lot, /giovane [1] https://atlas.ripe.net/docs/data_struct/#v4750_dns [2] https://en.wikipedia.org/wiki/Round-trip_delay_time

3 2

Atlas problems this morning?
by Stephane Bortzmeyer 01 Jul '19

01 Jul '19

#22170557, #22171022 and #22171068 terminate but no results are available. Is there some problem going on?

2 1

Search for Probe
by Sascha Groetzner 01 Jul '19

01 Jul '19

Hello, I would like to take part at the ripe atlas grip. I applied already for a probe and still waiting for delivery since a long time. Does anyone have a probe which isn`t in use or would like to transfer? best regards Sascha Sent via RIPE Forum -- https://www.ripe.net/participate/mail/forum

2 1

Streaming API Losses
by Marcel Flores 28 Jun '19

28 Jun '19

Hi all, We've been exploring the use of the Streaming API to collect result stream data for a set of user defined measurements, in particular using the interface available in Cousteau. However, we've found that the Streaming API seems to be "lossy", with only a fraction of the results reported through the usual system making their way into the stream. I've not been able to find any sort of pattern on what does and doesn't make it through. Does anyone else have experience with this? Are there known limitations with the Streaming API? If so, has anyone worked out any clever workflows to accommodate? Thanks very much! -- *Marcel Flores, PhD* | Sr. Research Scientist research.verizondigitalmedia.com | AS15133 <https://www.peeringdb.com/asn/15133> p: +1 310.593.6880 e: marcel.flores(a)verizondigitalmedia.com 13031 W Jefferson Blvd. Building 900, Los Angeles, CA 90094

1 0

Filter for all results of a probe within a given timeintervall
by Lars Prehn 28 Jun '19

28 Jun '19

Hi everyone, I'm currently trying to retrieve ping and/or traceroute results for a specific probe in a given time interval via cousteau and/or the measurement API directly. It seems like I'm not clever enough to get it done. Is there a possibility to achieve this goal without iterating over each and every measurement to check whether or not the probes and the time match? Best regards, Lars

1 0

raspbian.net/raspbian.org ipv6 peering problems
by Thomas Schäfer 25 Jun '19

25 Jun '19

Hello, I am not sure if I am right here with my question. Does someone measurements to the server of "raspbian"? Their hoster (bytemark, iomart, zayo?) seems not to be able to establish correct peerings. At least the peering to AS3320 is broken. I already contacted 3320. They say zayo doesn't fulfill the minimum security requirements. Are more peerings broken? Regards, Thomas

4 5

When to consider a measurement finished
by Wouter de Vries 25 Jun '19

25 Jun '19

Hi all, I am currently trying to do some measurements according to the following steps: 1. create a one-off measurement 2. wait for it to finish, by periodically polling the msmid and checking the status. 3. fetch the results However, the system takes a pretty long time to set the status to finished, even when all results are already in (maybe 10 minutes?). What heuristics/method do you recommend to determine whether to consider a measurement as finished? One option I consider is to periodically fetch all results for a given msmid and checking if the number of results matches the number of probes assigned to the measurement. However, I suspect that causes a much higher load on the infrastructure. Best regards, Wouter de Vries

3 2

Probe off-line for 6 days due to bad firmware signature
by Novak Jirka 25 Jun '19

25 Jun '19

Hello, my probe 22424 is off-line due to bad firmware signature error. I try to boot it without USB stick many times, then i change the USB stick (replace the old one with new one), but it doesnt solve my problem. Could you help me? This is the information from my status page: Bad Firmware Signature What does this mean? The probe's firmware signature is wrong. How can I fix this? Power-cycle the probe and wait for a couple of hours. If probe doesn't come online you should try to reinitialise or even replace your flash drive. Please use the following procedure: 1. Unplug the probe from its power source 2. Remove the USB stick from the probe 3. Plug in the probe WITHOUT the USB stick 4. Wait for ten minutes 5. Insert the USB stick If it didn't help repeat these steps using another working USB stick that is at least 4GB in size. NOTE: This must be done on a network with working DHCP! It will NOT work if you have configured your probe to use a static IP address, because this mini-operating system does not have access to any statically configure IP addresses or DNS resolvers. If you have configured your probe to use a static IP address, the only thing you can do is move it to a network with working DHCP. When the probe is listed as "connected" again, it is safe to move the probe back to its original location. However, please note that we advise configuring your probe to use a static IP address only if you feel it is truly necessary to do so. Thx, Jiri

3 5

any clue rtt unreachable packet loss 100% com234.476.249
by kiran.gunana＠colruytgroup.com 25 Jun '19

25 Jun '19

Hello, Can some one help me with the reason behind me always getting RTT unreachable and packet loss 100% for every probe I choose to monitor one our service from internet in belgium. Is there something I am not doing right or can guid me a better way of doing it. Even though there is 100% packet loss , my credit balance is still being consumed. Kiran Gunana Network Engineer kiran.gunana(a)colruytgroup.com T +32 2 363 55 45 (Ext : 55711) Colruyt Group Edingensesteenweg 196 - 1500 Halle www.colruytgroup.com LinkedIn Twitter Dit bericht is onderworpen aan de voorwaarden beschikbaar op onze website Ce message est soumis aux conditions disponibles sur notre site web This message is subject to the terms and conditions available on our website

4 3

prometheus exporter atlas_exporter ripe atlas com234.553.762
by kiran.gunana＠colruytgroup.com 24 Jun '19

24 Jun '19

Hello, Is any body out there using "https://github.com/czerwonk/atlas_exporter" promethues exporter for exporting metrics from ripe atlas, started using it , wanted to know experience or best practices before spending more time on it. Only exporting ping metrics for now as explained in the article, any other metrics were tried and how were the results, any such help is appreciated :) Kind Regards, Kiran. Dit bericht is onderworpen aan de voorwaarden beschikbaar op onze website Ce message est soumis aux conditions disponibles sur notre site web This message is subject to the terms and conditions available on our website

1 0

Re: [atlas] any clue rtt unreachable packet loss 100% com234.553.190
by kiran.gunana＠colruytgroup.com 24 Jun '19

24 Jun '19

gboonie, Indeed you are right, I had the impression some thing else is breaking it, I did modify and got my results. rg, kiran ----- Original Message: com234.484.306 --------------------------------- From: Dave . (gboonie(a)gmail.com) To: kiran.gunana(a)colruytgroup.com Copy: ripe-atlas(a)ripe.net Subject: Re: [atlas] any clue rtt unreachable packet loss 100% com234.476.249 Date: 24 June 2019 (09:35) Hi, Your destination is not responding to ICMP (ping/traceroute). This is not an Atlas issue. Dave Op ma 24 jun. 2019 om 08:50 schreef <kiran.gunana(a)colruytgroup.com>: Hello, Can some one help me with the reason behind me always getting RTT unreachable and packet loss 100% for every probe I choose to monitor one our service from internet in belgium. Is there something I am not doing right or can guid me a better way of doing it. Even though there is 100% packet loss , my credit balance is still being consumed. Kiran Gunana Network Engineer kiran.gunana(a)colruytgroup.com T +32 2 363 55 45 (Ext : 55711) Colruyt Group Edingensesteenweg 196 - 1500 Halle www.colruytgroup.com LinkedIn Twitter Dit bericht is onderworpen aan de voorwaarden beschikbaar op onze website Ce message est soumis aux conditions disponibles sur notre site web This message is subject to the terms and conditions available on our website Dit bericht is onderworpen aan de voorwaarden beschikbaar op onze website Ce message est soumis aux conditions disponibles sur notre site web This message is subject to the terms and conditions available on our website

1 0

delete old measurements from ripe com234.474.800
by kiran.gunana＠colruytgroup.com 24 Jun '19

24 Jun '19

Hello , Is there a way we can delete old measurements in ripe atlas measurements tab. Thes one's which are marked should be deleted for me. Kiran Gunana Network Engineer kiran.gunana(a)colruytgroup.com Colruyt Group Edingensesteenweg 196 - 1500 Halle www.colruytgroup.com LinkedIn Twitter Dit bericht is onderworpen aan de voorwaarden beschikbaar op onze website Ce message est soumis aux conditions disponibles sur notre site web This message is subject to the terms and conditions available on our website

1 0

Mailing list unsubscribe
by Christian Seifert 23 Jun '19

23 Jun '19

Hi, please unsubscribe me from the [atlas] mailing list. thanks

1 0

Mailing subscription
by Noe Manapo 23 Jun '19

23 Jun '19

Hi team, Please I want to join the ripe-atlas mailing list. Thank you Best regard Noe Manapo

2 2

RIPE Atlas anchor resolver update
by Anand Buddhdev 19 Jun '19

19 Jun '19

Dear colleagues, All the RIPE Atlas anchors run a caching DNS resolver. This resolver is used to look up names when a measurement requests name resolution using a probe's resolver. We have been running an older version of BIND for this service. In the coming days, we will be upgrading the version of BIND to the latest stable version (9.14). This version has dropped many work-arounds for various forms of brokenness in other DNS implementations. The effect of this is that a small number of domains hosted on broken DNS implementations cannot be looked up by this newer version of BIND. If you are running a measurement that uses an anchor's local resolver, and you find that some domain names are failing to resolve, it may be caused by this upgrade. Regards, Anand Buddhdev RIPE NCC

1 0

Periodic Probes Outage
by Milad Afshari 17 Jun '19

17 Jun '19

Dear all, Hi Within past days I am experiencing some periodic outage of many probes here in Iran, since I have checked all my probes and their network connections status, I guess they have some issue for connecting to the RIPE Atlas infrastructure. https://atlas.ripe.net/probes/?public=4&status=&country=IR&search=&… please let me know your thoughts and opinions. Many thanks Milad

4 3

RIPE Atlas Software Probes Survey
by Alun Davies 17 Jun '19

17 Jun '19

Dear colleagues, We are working on making the RIPE Atlas measurement software available as an installable package so you can run RIPE Atlas probes entirely in software without the need of a dedicated physical device. We are interested in your feedback regarding this feature, and we are also looking for volunteers willing to partner with us and help package the software for various operating systems and platforms. Please send your feedback and let us know if you can support RIPE Atlas software probes by filling in this short survey: https://www.ripe.net/participate/forms/apply/atlas-probes/ <https://www.ripe.net/participate/forms/apply/atlas-probes/> Kind regards, Alun Davies RIPE NCC

1 0

Web interface for Create New Measurements does not work for me
by ripe＠brite.cz 11 Jun '19

11 Jun '19

https://atlas.ripe.net/measurements/form/ when I click Traceroute and enter an IP address, then "Create My Measurements" button on the bottom does not do anything, no error message. Tried various settings and Firefox, Edge, Chrome. Is it error on my side? Any idea? Thank you Jiri

3 3

RFC1918 probes
by Mayer Hans 22 May '19

22 May '19

Dear All, Looking at the result of a traceroute measurement I see very often that first hop has a RFC1918 address. These days a found a result where the first 3 hops are showing something like 192.168.x.y Of course this could falsify the result especially for response time. Is there a way to select only Atlas probes which are located in non RFC1918 networks ? If not it would be nice to have such a possibility. Kind regards Hans -- Ing. Dipl.-Ing. Hans Mayer Systems Administrator Information and Communication Technologies (ICT) International Institute for Applied Systems Analysis (IIASA) Schlossplatz 1 A-2361 Laxenburg, Austria Phone: +43 2236 807 Ext 215 Mobile: +43 676 83 807 215 Web: http://www.iiasa.at E-Mail: mayer(a)iiasa.ac.at Atlas probe: 35603 Note: If there is a disclaimer or other legal boilerplate in the above message, it is NULL AND VOID. You may ignore it.

3 5