- ripe-atlas - mailman.ripe.net

Probe connection not holding
by Andre Heinrichs 01 Jul '18

01 Jul '18

Hi everyone, Another day, another weird effect. My probe (29384) keeps losing its connection to the Atlas systems. That seems to happen since the backend problems from Saturday were fixed. I also noticed that my probe switched from ctr-nue13 which it was always connected with to ctr-ams15 after 18 June and yesterday it got connected to ctr-ams14 but lost that connection again quite fast. My questions again: is that (probes getting disconnected all the time) something anyone else sees? Is there something on Atlas‘ side wrong or has my probe somehow lost the ability to stay connected for periods of more than a couple of minutes? There are again no obvious problems with my internet connection. TIA, Andre

2 2

Problems with the RIPE Atlas backend systems
by Anand Buddhdev 30 Jun '18

30 Jun '18

Hi folks, We have some problems with the RIPE Atlas back-end systems. I don't yet know the cause, or when things will be fixed, but this is just to let you know that we're working on it. Regards, Anand Buddhdev RIPE NCC

2 1

Re: [atlas] again: Probe offline, network appears okay
by Steffen Scholz 30 Jun '18

30 Jun '18

Hi, just to confirm, I seem to be having the same problem. My probe was shown as disconnected while the LEDs on the device indicated otherwise. After performing a power cycle it's not reconnecting anymore. Regards, Steffen Sent via RIPE Forum -- https://www.ripe.net/participate/mail/forum

3 2

Re: [atlas] again: Probe offline, network appears okay
by Michael H 30 Jun '18

30 Jun '18

Hi. I've had the same problems from time to time. Mostly after a power loss or power disconnect. In the end I had to replace the drive to end this frequent behaviour. This article brought me to success: https://atlas.ripe.net/docs/troubleshoot-probe-issues/ Sent via RIPE Forum -- https://www.ripe.net/participate/mail/forum

1 0

again: Probe offline, network appears okay
by Andre Heinrichs 29 Jun '18

29 Jun '18

Ho everyone, I'm again seeing the problem that Atlas doesn't see my probe as connected although my network shows no problems. I just tried restarting the probe and now the probe sees itself unable to connect. Is there a known problem somewhere, anyone else seeing this behavior or is it something weird on my end? TIA, Andre

1 0

More probes with incorrect location
by Ponikierski, Grzegorz 29 Jun '18

29 Jun '18

Hi! I was making some measurements for Comcast and found 3 probes with incorrect location. Can we fix it? ;) Probe #25030 - probe description and traceroute from this probe suggests California but Atlas map shows Florida. I think it should be California. Traceroute from 25030 towards something in California. ----------------- 1 - 192.168.2.1 NA None NA 0.454ms 2 - 96.120.88.149 7922 None COMCAST-7922 - Comcast Cable Communications, LLC, US 9.291ms 3 - 68.87.196.117 7922 be-20022-rur02.santaclara.ca.sfba.comcast.net COMCAST-7922 - Comcast Cable Communications, LLC, US 8.880ms [...] Probe #32240 - probe description suggests Caribean, map the same but traceroute suggest something in North-East of US. I think that traceroute is right. Traceroute from 32240 towards something in Ashburn. ----------------- 1 - 192.168.109.1 NA None NA 0.446ms 2 - 10.0.0.1 NA None NA 1.670ms 3 - 96.120.64.153 7922 None COMCAST-7922 - Comcast Cable Communications, LLC, US 9.171ms 4 - 96.108.56.17 7922 None COMCAST-7922 - Comcast Cable Communications, LLC, US 9.776ms 5 - 68.85.106.69 7922 be-50-ar01.needham.ma.boston.comcast.net COMCAST-7922 - Comcast Cable Communications, LLC, US 10.496ms 6 - 68.86.90.173 7922 be-1003-pe02.onesummer.ma.ibone.comcast.net COMCAST-7922 - Comcast Cable Communications, LLC, US 9.908ms [...] Probe #22575 - probe description and map suggests UK but traceroute clearly shows it's in Seattle. I think that traceroute is right. Traceroute from 22575 towards something in Seattle. ----------------- 1 - 10.20.30.1 NA None NA 0.519ms 2 - 96.120.100.81 7922 None COMCAST-7922 - Comcast Cable Communications, LLC, US 11.700ms 3 - 68.87.206.221 7922 po-118-rur201.bellevue.wa.seattle.comcast.net COMCAST-7922 - Comcast Cable Communications, LLC, US 9.210ms [...] Regards, Grzegorz

1 0

Error: Only anchors may be targeted.
by Mozafary Mohammad 28 Jun '18

28 Jun '18

Hello I've got "Only anchors may be targeted." on HTTP measurement creation.Any body can advise what the problem is? Thanks

8 9

Re: [atlas] Probe offline, Network appears okay
by Andi Meuli 18 Jun '18

18 Jun '18

Oh, nice. After several reboots and switching to a different USB power device it finally works again!? :-) Don't know what's different, but at least here in my company's network it is running well. -Andi Sent via RIPE Forum -- https://www.ripe.net/participate/mail/forum

3 3

Re: [atlas] Probe offline, Network appears okay
by Andi Meuli 18 Jun '18

18 Jun '18

Same here with probe 31884. Interestingly I have a Fritzbox at home as well. I discovered no problems with the network at home, the services worked as expected and as a test I changed the DNS from the provider to 8.8.8.8 and 8.8.4.4. Which did not helped. As a last step, I transferred the probe temporarily to the company network and have the same issue. Sent via RIPE Forum -- https://www.ripe.net/participate/mail/forum

2 2

Probe offline, Network appears okay
by Andre Heinrichs 18 Jun '18

18 Jun '18

Hi everyone. It looks like my Probe 29384 is offline since my Fritzbox went through the disconnect every 24 hours. This time the probe‘s LEDs (blinking number 3 and 4) tell me thatvthe Probe sees itself as not connected. My internet acces otherwise looks okay, so I’m guessing that it might be something on the other side. I can’t check the SOS requests as the current doesn’t seem to send any after the USB is initialized. TIA, Andre Heinrichs. PS: I tried rebooting the Probe already. That didn’t help.

1 0

Detecting open resolvers with atlas
by Eduardo Duarte 15 Jun '18

15 Jun '18

Hello all, I was wondering if anyone as done any work using Atlas probes to detect open resolvers on the network? I try to find in the RIPE Labs articles works around this problematic but didn't find anything. Thank you, -- Eduardo Duarte Direção de Infraestruturas e Sistemas l Systems and Infrastructure Director *DNS.PT* Rua Latino Coelho, n.º 13, 5.º piso | 1050-132 Lisboa | Portugal Tel: (+351) 211 308 200 Fax: (+351) 211 312 720 dns.pt <http://www.dns.pt> | dnssec.pt <http://www.dnssec.pt> | 3em1.pt <https://www.3em1.pt> | facebook.com/dns.pt <https://www.facebook.com/dns.pt> | pt.linkedin.com/in/dnspt <http://pt.linkedin.com/in/dnspt> Aviso de Confidencialidade/Disclaimer: Este e-mail foi escrito de acordo com o novo acordo ortográfico. Esta mensagem é exclusivamente destinada ao seu destinatário, podendo conter informação CONFIDENCIAL, cuja divulgação está expressamente vedada nos termos da lei. Caso tenha recepcionado indevidamente esta mensagem, solicitamos-lhe que nos comunique esse mesmo facto por esta via devendo apagar o seu conteúdo de imediato. This message is intended exclusively for its addressee. It may contain CONFIDENTIAL information protected by law. If this message has been received by error, please notify us via e-mail and delete it immediately. [ Antes de imprimir esta mensagem pense no ambiente. Before printing this message, think about environment ]

2 1

New on RIPE Labs: 2018 Campaign to Sponsor 10 RIPE Atlas Anchors
by Alun Davies 15 Jun '18

15 Jun '18

Dear colleagues, This morning we published an article looking at the RIPE NCC’s 2018 campaign to sponsor ten RIPE Atlas anchors. This is a repeat of the successful campaign we ran last year. The article contains all the details on criteria for applicants and how to apply: https://labs.ripe.net/Members/alun_davies/2018-campaign-to-sponsor-10-ripe-… <https://labs.ripe.net/Members/alun_davies/2018-campaign-to-sponsor-10-ripe-…> Best regards, Alun Davies

2 1

No probes working today?
by Stephane Bortzmeyer 14 Jun '18

14 Jun '18

DNS measurements don't start today, no probes are selected for a long time. See for instance <https://atlas.ripe.net/measurements/14367678/> (long delay) or <https://atlas.ripe.net/measurements/14369565> (no probes)

3 4

Running a probe behind a NAT66
by Roman Mamedov 13 Jun '18

13 Jun '18

Hello, I am trying to run a probe (#73) behind an IPv6 NAT. The probe gets an IP in a non-standard prefix 66:113::/64, which is then NATed to a single GUA IPv6. This used to work fine for a few months, but then in April-2018 problems started: the probe would connect to Atlas for 5-10 minutes, then disconnect for about 20 minutes, then connect again; this alternates over and over again. However -- if IPv6 RAs are enabled some time after the probe is powered-on (i.e. the controller connection already got established over IPv4), things seem to go on fine, i.e. the controller is connected over IPv4 for days, but various measurements are performed on IPv6 too. So it seems that only the controller connection is the problem. I fully expect that you didn't account for such a setup in the controller infrastructure or possibly various "local IP is valid" checks and whatnot, but why this used to work fine before? Has there been any change on your side in April that would break this kind of setup? -- With respect, Roman

5 8

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