- ripe-atlas - mailman.ripe.net

For help: launching a periodical atlas measurement
by Yihao Jia 19 Jul '18

19 Jul '18

Dear all, I am so sorry for using a screenshot for my last email. And I'd like to redescribe the problem I have. I'd like to launch a periodic Ping measurement (with python). It starts at UTC-now to (for example) 5 minutes later. I'd like the probe do the Ping test in every 1 minute. Thus I can have 5 results in this measurement. I am a little confused because all example on documents is one-off. I guess error might happen around "is_oneoff", "interval", "spread". source code for this test is below and in the attachment. Could you help me in checking where I get wrong? Many thanks, Yihao ---------------------------------------------------------------------------------------------- from datetime import datetime, timedelta from ripe.atlas.cousteau import ( Ping, AtlasSource, AtlasCreateRequest ) ATLAS_API_KEY = "" source2 = AtlasSource( requested=1, type="probes", value="35704" ) ping = Ping( af=4, target="202.112.51.179", description="Test for periodic Ping test", packets=1, ) def request(): atlas_request = AtlasCreateRequest( start_time=datetime.utcnow(), stop_time=(datetime.utcnow() + timedelta(minutes=5)), key=ATLAS_API_KEY, measurements=[ping], sources=[source2], is_oneoff=False, interval=60, spread=60 ) (is_success, response) = atlas_request.create() return is_success, response if __name__ == '__main__': is_success, response = request()

1 0

Need help in launching a periodical atlas measurement
by Yihao Jia 19 Jul '18

19 Jul '18

Dear all, I am in trouble with launching a periodical Ping measurement. [image: image.png] my script is like this, but my measurement always fails. I tried several times with different modification on "interval" and "spread". [image: image.png] one failed example can be reviewed here: https://atlas.ripe.net/measurements/15282285/ It works well when I launch a one-off measurement, but every time I try to launch a periodic measurement with the setting above, it fails all the time. it probably because the "is_oneoff", "interval", "spread" is set wrong, but I can't find a good example for it. The idea of this test measurement is to start a Ping test every 1 minute, from UTC-now to 5 minutes later. Thus, I'd like to have 5-set result in this measurement. Could you help me check where I set wrong? Many thanks, Yihao

3 2

DNS measurement using the Probe's resolvers
by Rami Al-Dalky 18 Jul '18

18 Jul '18

Hi Everyone, I have a question about using the probe's list of resolvers when creating a DNS measurement. It is unclear to me whether the probe would send the query to all resolvers at the same time or not! Also, does the probe send the query to all resolvers in its list or to a subset of those resolvers? Is DNS eyeball implemented in the probes? Sincerely, Rami

3 2

Transfer Anchor ownership
by Clément Hertling (Wxcafé) 17 Jul '18

17 Jul '18

Hi, We have an anchor at the company I work for that has been associated with the wrong RIPE Atlas account. We're trying to move it from that (personal) atlas account to a shared netops account, but can't find a way to do this. Is there a way to do this ourselves, or can someone from RIPE Atlas do it for us? Cheers, -- Clément 'wxcafé' Hertling

2 1

Wrong TLSA for stat.ripe.net
by Alarig Le Lay 10 Jul '18

10 Jul '18

Hi, Since one week or so, I have a TLSA validation error for stat.ripe.net on TCP/443 at each time I visit https://atlas.ripe.net/ and I have the same result from the RIPE nlnog node: alarig@airmure ~ % echo '' | openssl s_client -connect atlas.ripe.net:443 2>/dev/null | openssl x509 -in /dev/stdin -fingerprint -sha256 | grep SHA256 | sed 's/://g' | cut -d '=' -f 2 8248E13AB5CA3BACAC63F15B831DA32F2CD54973EDF74E69B6A614B7295C02B4 alarig@airmure ~ % dig +short -t TLSA _443._tcp.atlas.ripe.net | awk '{ print $4 $5 }' 8248E13AB5CA3BACAC63F15B831DA32F2CD54973EDF74E69B6A614B7295C02B4 alarig@airmure ~ % echo '' | openssl s_client -connect stat.ripe.net:443 2>/dev/null | openssl x509 -in /dev/stdin -fingerprint -sha256 | grep SHA256 | sed 's/://g' | cut -d '=' -f 2 2A2B939449E847374121D4846E3117F23A0283C7B2818ED96C91D2808ABE4C0E alarig@airmure ~ % dig +short -t TLSA _443._tcp.stat.ripe.net | awk '{ print $4 $5 }' E3DC43427AA9F62D1E07BBE108AF62BEE84A454DB579FD57A4FFDFFD5A23E576 grifon@ripe01:~$ echo '' | openssl s_client -connect stat.ripe.net:443 2>/dev/null | openssl x509 -in /dev/stdin -fingerprint -sha256 | grep SHA256 | sed 's/://g' | cut -d '=' -f 2 2A2B939449E847374121D4846E3117F23A0283C7B2818ED96C91D2808ABE4C0E grifon@ripe01:~$ dig +short -t TLSA _443._tcp.stat.ripe.net | awk '{ print $4 $5 }' E3DC43427AA9F62D1E07BBE108AF62BEE84A454DB579FD57A4FFDFFD5A23E576 The commands are ugly but work on atlas.ripe.net. Could you please update it? Regards, -- Alarig Le Lay

1 0

New on RIPE Labs: Comparing Virtual and Metal RIPE Atlas Anchors
by Mirjam Kuehne 04 Jul '18

04 Jul '18

Dear colleagues, We compared performance between virtual and physical RIPE Atlas anchors. Please find the results on RIPE Labs: https://labs.ripe.net/Members/stephen_strowes/comparing-virtual-and-metal-r… Kind regards, Mirjam Kühne RIPE NCC

1 0

Probe seems DoA
by Benoit Lelievre 03 Jul '18

03 Jul '18

Yesterday I received two v3 probes. While the first one took a while to update and connect the second one is showing a different behaviour. When I plug it in the reset light flashes for about 10 second but then the second LED lights up solid and it seems like the probe is frozen. It doesn't even request an IP address from my DHCP server. The FAQ doesn't list what only having LEDs 1 and 2 on solid means and I'm concerned that this probe is bricked. Any advice on what I should do with this probe? Sent via RIPE Forum -- https://www.ripe.net/participate/mail/forum

2 3

New on RIPE Labs: Outcome of the RIPE Atlas Anchor VMs Pilot
by Mirjam Kuehne 02 Jul '18

02 Jul '18

Dear colleagues, The pilot we ran to assess the feasibility of involving virtual machines in the pool of RIPE Atlas anchors is complete and the results are good. Please find more details on RIPE Labs: https://labs.ripe.net/Members/kistel/outcome-of-the-ripe-atlas-anchor-vms-p… Kind regards, Mirjam Kühne RIPE NCC

1 0

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