- ripe-atlas - mailman.ripe.net

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