- ripe-atlas - mailman.ripe.net

RIPE Atlas CLI tools docker image
by Anurag Bhatia 26 Apr '21

26 Apr '21

Hello everyone, A little while ago I put RIPE Atlas CLI tools docker image based on alpine. - https://hub.docker.com/r/anuragbhatia/ripe-atlas-tools It stores the API keys at ~/.config on the host (and that is mounted inside the container). Dockerfile can be found here <https://github.com/anuragbhatia/ripe-atlas-tools/blob/master/Dockerfile> and one can use it to build image locally if intended to. *Example usage: * docker run --rm -v ~/.config:/root/.config -it anuragbhatia/ripe-atlas-tools ripe-atlas measure traceroute --from-country IN --target he.net One can set an alias in the local shell to make it appear almost like a locally installed setup. E.g on fish: anurag@Anurags-MacBook-Pro ~> alias ripe-atlas='docker run --rm -v ~/.config:/root/.config -it anuragbhatia/ripe-atlas-tools ripe-atlas' anurag@Anurags-MacBook-Pro ~> funcsave ripe-atlas anurag@Anurags-MacBook-Pro ~> Thus the reduces syntax is alias becomes: ripe-atlas measure traceroute --from-country IN --target he.net Please do share if anyone has any feedback. -- Anurag Bhatia anuragbhatia.com

1 0

Filtering measurements
by Sanaa GHANDI 23 Apr '21

23 Apr '21

Hello, I hope you are all doing well. I have a few questions concerning the measurements selection, and I am interested only on the anchoring mesh measurements. In fact, for optimisation issues, I would like to be able to select only measurements of interest: For example, I want to get the results coming from sources: X and Y, and targeting the anchor 6771. Now I can get the measures targeting the anchor 6771 using this code from Altas Cousteau ################################################################## from ripe.atlas.cousteau import MeasurementRequest filters = {'tags': ['anchoring','mesh',6771] } measurements = MeasurementRequest(**filters) #################################################################### But I have no idea of how to make a filter on the sources as well, since all we can access through the measurements are the number of anchors requested and not their ids. Do you know a way to get access to the sources of a measurement via Atlas Cousteau or another Ripe Tool ? Thank you -- Sanaa

4 4

Custom box and bag
by Slite 22 Apr '21

22 Apr '21

Hello, Have a nice day. Does your company needs any Custom packaging box/bags for your products? We are Chinese supplier who can produce customized packaging/bag with custom logo. Dear,we have cartons,cardboard box,plastic box,metal tin box,paper bag,plastic bag,non-woven bag ... to pack your products. Then tell me which one you want,I will give you best price with good service. Any of your reply will be appreciated. Looking forward to your reply. Best regards, Slite Contact Email: slite(a)slcpackage.com What's app: 0086 15314679598SLC-PACKAGE CO. LTDwww.slcpackage.com www.slcpackages.comContact Person: Slite Cao Address:1406, No 11,Dongyue Huayuan,Nancheng,Xinluo,Longyan,Fujian,China If you no longer wish to receive mail from us, you can <http://tracking.littleindustrial.info/tracking/unsubscribe?d=hV-G-DkT38mtq2…> Unsubscribe

1 0

Request for credits for research
by Mohan, Nitinder 20 Apr '21

20 Apr '21

Dear RIPE community, I hope you are all safe and sound. I am a Postdoctoral fellow at the Technical University of Munich, Germany. We are currently working on an ongoing research project which aims to analyze the availability and reachability of cloud data centers globally. The first work of our work will appear in ACM HotNets 2020 titled "Pruning Edge Research with Latency Shears" (http://conferences.sigcomm.org/hotnets/2020/program.html). We are currently preparing the camera-ready version of the paper and will share it with the community by hosting it (and the associated dataset) publicly soon. We are currently planing to submit the second leg of our work to a conference with submission deadline a month. In order to complete all set of measurements for required analysis, we are scheduling very large-scale measurements over the platform which has burned through almost all our credits and left us in need. I have always found the RIPE Atlas community to be helpful and generous towards research and I am hoping that you could support our research by donating us some of your spare credits. Your help will be highly appreciated. My RIPE account is nitinder.mohan(a)helsinki.fi Thanks and Regards Nitinder Mohan Postdoctoral Fellow Technical University of Munich, Germany <http://www.cs.helsinki.fi/u/nmohan/>https://www.nitindermohan.com/

15 18

Feature request for Validated Timestamps
by Will 15 Apr '21

15 Apr '21

I was starting to work on a mapping measurement project where I wanted to delegate measurements to remote machines. There are a number of schemes that have been used where a not fully trusted node can come away from a measurement with a record that can be used to verify that it actually made the measurement. Many of these make use of a time stamp signed by the "server" as a way to prevent replaying old measurements. Things that have been done with this feature also include tlsnotary[1], which works with web servers where the "server random" bytes of the tls handshake includes the server timestamp (the default for openssl). The implementation of ssl currently used by probes does not appear to include the timestamp in the server hello. Another approach would be to add a "roughtime" service on probes Interested to hear if there would be willingness to have probe software support something in this direction. [1] https://tlsnotary.org/ --Will

5 9

Spurious "would violate your maximum daily spending limit"
by Stephane Bortzmeyer 07 Apr '21

07 Apr '21

I receive a: {"error":{"detail":"There was a problem with your request","status":400,"title":"Bad Request","code":102,"errors":[{"source":{"pointer":""},"detail":"Executing this measurement request would violate your maximum daily spending limit of 1000000.0 credits. Please stop some of your currently running measurements and try again."} from the API. The request is: {'is_oneoff': True, 'definitions': [{'description': 'DNS resolution of use-application-dns.net./A from AS #3215', 'af': 4, 'type': 'dns', 'query_argument': 'use-application-dns.net.', 'query_class': 'IN', 'query_type': 'A', 'set_rd_bit': True, 'protocol': 'UDP', 'use_probe_resolver': True}], 'probes': [{'requested': 100, 'type': 'asn', 'value': '3215', 'tags': {'include': ['system-ipv4-works', 'system-resolves-a-correctly', 'system-resolves Which is very small. I run this sort of requests frequently. My daily expenditure is small (13,680 credits). Why is it rejected?

3 5

What to do with broken v1 probe?
by Lorenzo Colitti 30 Mar '21

30 Mar '21

Fellow atlas users, After more than 10 years (!) of 99% uptime (see below), my probe v1 appears to have given up the ghost. When connected to power, the lights still come on, but after a few seconds link bounces, and it never sends any packets. Any idea what to do? Should I just apply for a new probe? Are new probes being given out these days? Cheers, Lorenzo ---------- Forwarded message --------- From: RIPE Atlas <no-reply(a)ripe.net> Date: Tue, Nov 24, 2020 at 9:59 PM Subject: Congratulations! Your RIPE Atlas probe 333 is 10 years old! To: Lorenzo Colitti <lorenzo(a)colitti.com> Dear Lorenzo Colitti, It's your probe's birthday today !! To celebrate that fact, we are giving you 9869024 credits to use for scheduling your own measurements. In the last 10 years your probe was connected for 99% of the time. Happy measuring and thank you on behalf of everyone at the RIPE NCC and the other RIPE Atlas users. The RIPE Atlas Team

7 6

Re: [atlas] Probe location obfuscation
by Ponikierski, Grzegorz 26 Mar '21

26 Mar '21

I would add to it additional problem that some hosts obfuscate probe location even more. For example you can find probes which in reality are located in US but are marked as CN or probes which are in reality in Wisconsin but are marked in California. Of course these are extreme cases. I guess most hosts just put a pin with probe location just somewhere around where it's locate as long it's in the same city. I don't remember, as a host of 3 probes, to get any precise recommendations how to mark probe location. Personally I just put a pin in city district where probe is locate. Regards, Grzegorz From: "Mccherry, Paul (Student)" <p.mccherry(a)lancaster.ac.uk> Date: Thursday 2021-03-25 at 11:20 To: "ripe-atlas(a)ripe.net" <ripe-atlas(a)ripe.net> Subject: [atlas] Probe location obfuscation Can anyone confirm the geo-location obfuscation of probes as being up to 1km as per https://atlas.ripe.net/about/faq/#are-the-locations-of-probes-made-public<https://urldefense.com/v3/__https:/atlas.ripe.net/about/faq/*are-the-locati…> I am a Phd student carrying out research on the RIPE atlas platform and an early result seems to indicate 1 probe has an obfuscation of 10km distance but this may be an anomaly or perhaps something not taken into account as yet.

10 13

Unused Probes (was: What to do with broken v1 probe?)
by Sylvain Baya 25 Mar '21

25 Mar '21

{change the subject [0]} Dear all, Hope you are doing well! Le lun. 22 mars 2021 10:35, Estelmann, Christian <c.estelmann(a)gmx.net> a écrit : > Is there a possibility to return no longer used probes? Hi Christian, Thanks for your email brother. ...imho, it's a very useful idea! Within one [1] of our NOG's activities we have included the recovery of unused probes ; but maybe we should have tried it the other side...by asking probe's hosters to send it to an other volunteer or to us, if they become unable to keep it online... __ [1]: FR <https://www.cmnog.cm/dokuwiki/IdeasAndProjects:Projects:AtlasCM> I have one which was homed at a now closed location. Someone else could > give it a new home. > ...i suggest that you write to your ccNOG's mailinglist to find the nearest volunteer who could want to host your protected probe ;-) ...hope this could help. Blessed thursday! __ [0]: <https://lists.ripe.net/pipermail/ripe-atlas/2021-March/004638.html> Shalom --sb. > Greeting, > Christian > > Am 21. März 2021 17:14:57 MEZ schrieb Chriztoffer Hansen <ch(a)ntrv.dk>: > >On Sun, 21 Mar 2021 at 08:18, Lorenzo Colitti via ripe-atlas wrote: > >> After more than 10 years (!) of 99% uptime (see below), my probe v1 > >appears to have given up the ghost. [...] > >Cheers, > >Chriztoffer > > -- -- Best Regards ! __ baya.sylvain[AT cmNOG DOT cm]|<www.cmnog.cm/dokuwiki> Subscribe to Mailing List: <lists.cmnog.cm/mailman/listinfo/cmnog/> __ #‎LASAINTEBIBLE‬|#‎Romains15‬:33«Que LE ‪#‎DIEU‬ de ‪#‎Paix‬ soit avec vous tous! ‪#‎Amen‬!» ‪#‎MaPrière‬ est que tu naisses de nouveau. #Chrétiennement‬ «Comme une biche soupire après des courants d’eau, ainsi mon âme soupire après TOI, ô DIEU!»(#Psaumes42:2)

1 0

Probe location obfuscation
by Mccherry, Paul (Student) 25 Mar '21

25 Mar '21

Can anyone confirm the geo-location obfuscation of probes as being up to 1km as per https://atlas.ripe.net/about/faq/#are-the-locations-of-probes-made-public I am a Phd student carrying out research on the RIPE atlas platform and an early result seems to indicate 1 probe has an obfuscation of 10km distance but this may be an anomaly or perhaps something not taken into account as yet.

1 0