- ripe-atlas - mailman.ripe.net

Re: [atlas] Your RIPE Atlas Probe (ID: 17523) is not connected to our network
by Joachim Tingvold 05 Aug '15

05 Aug '15

On 3 Aug 2015, at 1:40, RIPE Atlas wrote: > We have noticed that your probe (#17523 with description SHL46-jocke) > is not connected to our infrastructure and has been disconnected since > 2015-07-26 23:39 UTC. Hi, Having some issues getting my probe to work in an v6-only environment. Doing only SLAAC (and no v4) made it unable to connect (which makes kinda sense). Made it connect temporarily via v4 so that I could set static v6-address and DNS. Waited a while, then removed v4. I could see it on the ND-table of my router, and it even replied to ping on the static v6 address I assigned it. However, it still showed up as "offline" on the Atlas portal. After some mocking around, it now seems to be in some kind of stale status (the switchport doesn't even learn the MAC address of the probe). Any takers? (-: -- Joachim

2 1

[User Defined Measurements] status settings
by sarah.wassermann＠student.ulg.ac.be 04 Aug '15

04 Aug '15

Hi, In the context of a research internship, I am automatising tools to check whether measurements have finished or not. Could you please tell me what the different status settings are? In the docs, only "scheduled", "ongoing" and "stopped" are indicated, but for 2 of my measurements I came across the status "failed" and "no suitable probes". Thank you very much in advance for your help! Sarah Wassermann

2 1

Strange certificates at probe 17009
by Stephane Bortzmeyer 01 Aug '15

01 Aug '15

Probe #17009, located in Bangkok, when asked to perform a "sslcert" measurement, always retrieve a certificate whose expiration date is 2024-10-31, whatever the target is. There is probably a man-in-the-middle before the probe...

4 3

[UDM] Consistency in the timeout parameter
by Stephane Bortzmeyer 31 Jul '15

31 Jul '15

If I read correctly <https://atlas.ripe.net/docs/measurement-creation-api/>, traceroute and NTP measurements have a "timeout" parameter but not ping or DNS. Why?

2 3

ASN-information on Network tab
by Joachim Tingvold 29 Jul '15

29 Jul '15

Hi, Any reason as to why the ASN numbers isn't displayed on the "Network" tab of a probe that is public? The ASN numbers is available on the probes list, so it would be practical to show it on the "Network" tab as well. -- Joachim

2 3

APIs for accessing DNSMON data
by Brett Carr 29 Jul '15

29 Jul '15

Hello, last year there was a discussion on this list regarding API’s for accessing DNSMON data, I believe the intention was to discuss this at the Warsaw meeting, unfortunately I was not able to attend that meeting so I’m not really sure what the outcome of that discussion was. Nominet use DNSMON on a daily basis and would be very interested in using an API to access the data held in DNSMON. Thanks Brett -- Brett Carr Senior DNS Engineer Nominet UK

3 2

New on RIPE Labs: Extending RIPE atlas' Reach
by Vesna Manojlovic 24 Jul '15

24 Jul '15

Dear colleagues, we are about to start experimenting with new outreach methods, in an effort to increase the growth rate of connected RIPE Atlas probes and achieve better coverage across the globe. Read more in this RIPE labs article: https://labs.ripe.net/Members/becha/extending-ripe-atlas-reach Regards, Vesna Manojlovic Measurements Community Building

2 1

1msec RTT to ipv6.google.com?
by Abreu, Alexandre, Vodafone Portugal 22 Jul '15

22 Jul '15

Hi all Anyone had any issues with wrong RTTs on IPv6 probes? I've setup a ping probe (ID#2143865) to ipv6.google.com and it's consistently giving 1msec RTT on the seismograph and the json file. It is physically impossible. This is the RTT I get on the CPE the probe is connected to: SEQ HOST SIZE TTL TIME STATUS 0 2a00:1450:4003:806::200e 56 59 12ms echo reply 1 2a00:1450:4003:806::200e 56 59 12ms echo reply 2 2a00:1450:4003:806::200e 56 59 12ms echo reply 3 2a00:1450:4003:806::200e 56 59 12ms echo reply 4 2a00:1450:4003:806::200e 56 59 12ms echo reply 5 2a00:1450:4003:806::200e 56 59 12ms echo reply Regards, Alexandre Abreu

5 7

Probe downtime alert for IPv6?
by Jeroen van der Ham 21 Jul '15

21 Jul '15

Hi, The portal offers a notification option for down time. I have a probe that is connected both over IPv4 and IPv6. The latter is through an IPv6 tunnel, which seems a bit flaky at times. I was hoping that the downtime notification would also hold for IPv6, but it turns out it doesn’t. Would it be possible that that be added? Thanks, Jeroen.

2 1

atlas.ripe.net site 302 redirect loop
by Yang Yu 20 Jul '15

20 Jul '15

I have been having this issue with every feature that requires logging in on https://atlas.ripe.net. For instance, when I try to create an API key, HTTP POST to /keys/create/ gets a 302 to https://atlas.ripe.net/login?next=/keys/create/, then the new GET results in another 302 to https://atlas.ripe.net/keys/create/ and back to https://atlas.ripe.net/login?next=/keys/create/ until the browser gives up on redirecting and throws an error. Tested on Chrome/Firefox with Ubuntu trusty and Windows 7. Tried on a different computer from a different continent, still the same issue.

3 2