- ripe-atlas - mailman.ripe.net

Re: [atlas] Probe with ever changing upstreams/ASs?
by stephane＠mouton.com 12 Nov '23

12 Nov '23

+ripe-atlas Regards, Grzegorz From: "Ponikierski, Grzegorz" <gponikie(a)akamai.com> Date: Thursday, 3 August 2023 at 17:49 To: Carsten Schiefner <carsten(a)schiefner.de> Subject: Re: [atlas] Probe with ever changing upstreams/ASs? Hi! It depends on use case. For me, such probe would be fine for one-off measurements but for continuous measurements I would filter out such probe to avoid noise in data. However, when I looked on freifunk.net map I noticed that this network span across Germany, Switzerland, and Austria so even for one-off measurements usage of such probe is questionable because I never know where remote end of the tunnel is. If I understand correctly it can jump from country to country every day. In other words, such probe would be tricky to handle and user will have to be aware how such probe behave to properly handle data generated by it. Probably new system tag would be needed to mark such exotic probe. Regards, Grzegorz From: Carsten Schiefner <carsten(a)schiefner.de> Date: Thursday, 3 August 2023 at 15:07 To: "ripe-atlas(a)ripe.net" <ripe-atlas(a)ripe.net> Subject: [atlas] Probe with ever changing upstreams/ASs? All - I wonder whether this is a good idea or rather a really bad one... I have a free port on a Freifunk router where I could plug in a RIPE Atlas probe. Freifunk is a community where you - amongst other things - can offer a bit of your bandwidth to "the world". This connectivity sharing however is set up as a tunnel to various ISPs (for-profit companies and non-profit associations) as these would enjoy the "provider privilege": that in short is not to be held accountable for e.g. copy right infringements etc. ("Störerhaftung"). Anyhow: as part of this tunnel setup, the other end of the tunnel changes every 24 to 48 hours - and so does the upstream and therefore also the AS of the upstream provider. And now I am asking myself: a probe with ever changing upstreams/ASs - shall such an addition to the RIPE Atlas network be considered a fault or a feature? Any comments, anybody? Cheers, -C. -- ripe-atlas mailing list ripe-atlas(a)ripe.net https://urldefense.com/v3/__https://lists.ripe.net/mailman/listinfo/ripe-at… [1] -- ripe-atlas mailing list ripe-atlas(a)ripe.net https://lists.ripe.net/mailman/listinfo/ripe-atlas Links: ------ [1] https://urldefense.com/v3/__https:/lists.ripe.net/mailman/listinfo/ripe-atl…

1 0

decommission of virtual probes
by ripe.net＠toppas.net 07 Nov '23

07 Nov '23

Hello folks, dear Atlas team, I would like to discuss the case, where a virtual probe is decommissioned because the place where you ran it will no longer be available. For example, a VPS which you have rented somewhere, but you've decided to cancel that service. Does it make sense to create and keep a backup of the virtual probe, so that you can re-deploy it later (with another AS)? Or is it better to delete the virtual probe and create a new one? Also: is there an official way to decommission a virtual probe permanently? I felt like this could be interesting for other people too, so i decided to discuss this question publicly. BR, Simon

2 1

Re: [atlas] decommission of virtual probes
by ripe.net＠toppas.net 06 Nov '23

06 Nov '23

My bad. non-hardware probes are called "software probes" non-hardware anchors are called "virtual anchors" I mixed that up. I meant software probes. BR, Simon On 06.11.23 21:16, Ernst J. Oud wrote: > Define “virtual probe” please? Do you mean a SW probe? To me a SW probe is as real as a HW probe. > > Or do you mean an abandoned probe? > > Regards, > > Ernst J. Oud > >> On 6 Nov 2023, at 20:53, Simon Brandt via ripe-atlas<ripe-atlas(a)ripe.net> wrote: >> >> Hello folks, dear Atlas team, >> >> I would like to discuss the case, where a virtual probe is decommissioned because the place where you ran it will no longer be available. For example, a VPS which you have rented somewhere, but you've decided to cancel that service. >> >> Does it make sense to create and keep a backup of the virtual probe, so that you can re-deploy it later (with another AS)? Or is it better to delete the virtual probe and create a new one? >> >> Also: is there an official way to decommission a virtual probe permanently? >> >> I felt like this could be interesting for other people too, so i decided to discuss this question publicly. >> >> BR, >> Simon >> >> -- >> ripe-atlas mailing list >> ripe-atlas(a)ripe.net >> https://lists.ripe.net/mailman/listinfo/ripe-atlas

1 0

Customs value of Atlas Probe
by Christopher Munz-Michielin 06 Nov '23

06 Nov '23

Hi All, I'm fighting a bit of a battle over the value of the ripe atlas probe for the purposes of taxation (they are insisting it's value is more then $300 CAD and over $50 in taxes is owed to import it) and in order to fight this I need to provide proof of value, however, I obviously don't have a purchase receipt to show them. Is there any form that RIPE provides which shows the value of the Atlas probes for customs/import purposes that I can include with my case? Thanks!

2 2

New measurements listing page
by Stephen Suess 24 Oct '23

24 Oct '23

Hello Atlas friends, As part of our continuing improvements to the Atlas UI, we have just pushed a major update to the measurements listing page. Among the improvements: - Cleaner, simpler interface - Improved filtering and sorting - Views are sharable with all params - Improved paging - Favourite and Hide actions - and quite a bit more You can find the new page at https://atlas.ripe.net/measurements/ or in the menu under "Measurements", and the old page will remain available for a few weeks at https://atlas.ripe.net/measurements/legacy/. Your input and feedback is highly appreciated, you can reply to this message or directly to me or in the forum at https://forum.ripe.net/t/new-ripe-atlas-measurement-listing-page/725 Thanks! Stephen RIPE Atlas UI

1 0

Delays in web interface
by Ernst J. Oud 21 Oct '23

21 Oct '23

Hi, I experience that lots of graphs in the web interface don’t display, sometimes when clicking on the built-ins tab the “loading” never finishes etc. Measurements appear to run fine. Any performance problems in the back end or ripe stat? Regards, Ernst J. Oud

1 1

Questions with regard to the measurement status and running time
by Jerome Mao 20 Oct '23

20 Oct '23

Hi RIPE Atlas Team and Community, I would like to know more about the status of measurements - I have scheduled a one-off ping measurement which utilized 15 anchors. I polled the measurement status and results from my local desktop to the restful API through cousteau Python lib. The results were returned to me in less than a minute, but it took around 13 minutes for the measurement to transition from "ongoing" to "stopped." On the other side, the time delta between the "requested start time" and "requested stop time" on the RIPE Atlas portal is 9 minutes. My questions are: 1. Why is the measurement "ongoing" even if the results have already been made available? 2. What is the meaning of the "requested start time" and "requested stop time" on the RIPE Atlas portal? 3. Will a one-off measurement release one slot from the measurement rate limit once its result becomes available even if it’s still in "ongoing" state? Thanks! Best, Jerome

3 3

HE "Supertraceroute" exposes ATLAS traceroute functionality to the public
by me＠natha.info 19 Oct '23

19 Oct '23

Hi all, As mentioned by Lukas, NLNOG Ring is also used in the "supertraceroute" project from HE. The NLNOG Board just published a statement regarding this on the NLNOG mailing list: http://mailman.nlnog.net/pipermail/nlnog/2023-October/003099.html Kind regards, Nathalie Trenaman (also on the NLNOG Board)

2 1

HE "Supertraceroute" exposes ATLAS traceroute functionality to the public
by Lukas Tribus 19 Oct '23

19 Oct '23

Hello, FYI HE's new "supertraceroute" exposes ATLAS traceroute functionality to the public: https://bgp.he.net/traceroute/ Other sources are (NLNOG) RING nodes and other projects. Interesting approach, not sure if I should be happy about this, but I guess HE is paying for it with Atlas credits. Lukas

2 1

NTP empty results ('result': [{'x': '*'}])
by Giovane C. M. Moura 12 Oct '23

12 Oct '23

Hi folks, I am getting some NTP results in the following format: 'result': [{'x': '*'}], Does anyone know waht is this supposed to mean? is it like the measurement did not run? See blob below: {'fw': 5080, 'mver': '2.6.2', 'lts': 20, 'dst_name': '186.155.28.147', 'dst_addr': '186.155.28.147', 'src_addr': '10.10.31.19', 'proto': 'UDP', 'af': 4, 'result': [{'x': '*'}], 'msm_id': 47867316, 'prb_id': 33745, 'timestamp': 1671799154, 'msm_name': 'Ntp', 'from': '85.238.41.3', 'type': 'ntp', 'group_id': 47867316, 'stored_timestamp': 1671799249}] thanks, /giovane

2 1