- ripe-atlas - mailman.ripe.net

Processing RIPE Atlas data as Big Data
by BELLAFKIH hayat 24 Jul '18

24 Jul '18

Dear RIPE Atlas users, I am studying the processing of the data collected by the probes as a Big Data problem. For instance, one hour of traceroute data count for 500 Mo (bzip2), so 7 Go of data in text format. Can you share with me how you deal with these data in practice. are you using a super machine, Big Data tools? best regards, Hayat

2 1

Looking for advise and temporarily limits increment for research
by Yihao Jia 22 Jul '18

22 Jul '18

To whom it may help, My name is Yihao. I am a Ph.D. student. Recently I am doing a research with RIPE Atlas. However, my research requires many measurements in a short period, which breaks several rules of the Rate Limits. Since I really like and in hurry to use Atlas to support my research, is there any advice I can get from this? I'd like to describe why it would be necessary for my research. And if possible, may I get a temporarily limit increment for 10 days? Many thanks, Yihao Jia

3 3

Re: [atlas] Need help: launching a periodical atlas measurement
by Stephane Bortzmeyer 19 Jul '18

19 Jul '18

On Thu, Jul 19, 2018 at 10:47:54AM -0500, Yihao Jia <yhjia03(a)gmail.com> wrote a message of 192 lines which said: > 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. "is_oneoff" is off by default. "interval" is documented as "In normal (not one-off) measurements, this value represents the number of seconds between measurements by a single probe." I never tried "spread". I don't know the exact JSON you sent but this one worked (5 minutes, 1 minute between each test): {'definitions': [{'target': 'fr-ilm-as57119.anchors.atlas.ripe.net', 'af': 4, 'interval': 60, 'packets': 1, 'type': 'ping', 'description': 'Ping fr-ilm-as57119.anchors.atlas.ripe.net'}], 'start_time': 1532026200, 'stop_time': 1532026500, 'probes': [{'requested': 1, 'type': 'area', 'value': 'WW'}]} And it gave this measurement: https://atlas.ripe.net/measurements/15297080/

1 0

Inquiry: RIPE Atlas credits M Fung
by Matthew Fung 19 Jul '18

19 Jul '18

Hello, My name is Matthew, I am an undergrad studying CS at University of British Columbia. I've recently discovered the work done by RIPE and I'm really interested in using Atlas for a research project. I am wondering if anyone is willing to share credits in order to make this possible. I aim to use no more than 1M credits. (My user info is included below) Thanks, Matthew Fung RIPE ID: y6c0b(a)ugrad.cs.ubc.ca

2 1

Global Traceroute
by Steve Gibbard 19 Jul '18

19 Jul '18

I wrote front-end to traceroute from the RIPE Atlas probes. It looks like a standard looking glass — you select a probe by location and AS number, enter a destination, and it does a traceroute. It’s on the web at https://www.globaltraceroute.com. If this looks useful, please check it out and tell me what you think. One of the things I've found frustrating when troubleshooting routing problems was the lack of information about inbound paths. Various measurement systems would tell me when performance was bad. Traceroutes from my own network would tell me what path traffic to a destination was taking outbound. Flow systems would tell me what interface inbound traffic was coming in on, and sometimes what peer it was coming through. But determining the full path inbound traffic was taking — why users of some ISP in Asia were having their traffic show up at one of my POPs in Europe, for instance, was much more difficult. I’ve been using looking glasses and commercial performance monitoring systems that allow traceroutes from their probes, but those often weren’t where the end users were. RIPE Atlas did have probes where a lot of my end users were, so I started configuring one time measurements on RIPE Atlas whenever I needed a traceroute from a simulated end user. But finding a suitable probe and configuring the measurement was too cumbersome to do when I wasn’t pretty desperate. This is my attempt to solve that problem. Thanks, Steve

6 7

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