- ripe-atlas - mailman.ripe.net

Built-ins tab in Atlas web interface does not respond
by Ernst J. Oud 11 Sep '23

11 Sep '23

Hi, In the web interface clicking the tab “Built-ins” does not work, it shows “loading” and nothing happens. Tried different browsers. Regards, Ernst J. Oud

2 3

Fwd: Questions with regard to the measurement status and running time
by Ernst J. Oud 08 Sep '23

08 Sep '23

> From: "Ernst J. Oud" <ernstoud(a)gmail.com> > Date: 7 September 2023 at 20:46:53 CEST > To: Jerome Mao <jxm959(a)case.edu> > Subject: Re: [atlas] Questions with regard to the measurement status and running time > > My 0.02 euro; did you get the results of all 15 probes in that short period? I use Magellan to get results and after a minute sometimes not all results are in. Magellan has two options in the latest version; a timeout to stop streaming results after for instance 30 seconds or stop after a specified number of results have been received. > > I believe probes get instructions from controllers and ofcourse they don’t receive those all at the same time. Also probes might be busy I guess doing their default measurements (every 4 minutes). So it might take a while, I have seen results coming in after a couple of minutes. > > Not sure the above is correct, just my thoughts. > > Regards, > > Ernst J. Oud

2 1

Verdien 3.0.3
by Ernst J. Oud 07 Sep '23

07 Sep '23

Hi, @Chris Amin: Yes, commit c999953, version 3.0.3 completely solves this. My gratitude is larger than the losses Mr. Musk is making now that Twitter is going down the drain :-) Thanks! Regards, Ernst J. Oud

5 4

Probe issues - now recovered
by Nigel Metheringham 04 Sep '23

04 Sep '23

Probe Id 22680 This v3 probe started playing up a couple of months back but I had not had a chance to properly investigate until this weekend. Symptoms were that it disconnected and reconnected every minute or so - my August availability report was nearly 14K lines long! Packet trace showed that it was connecting to the RIPE atlas hosts on port 433 (but talking ssh), and after a minute or so was sent a FIN from the RIPE end. Tried a few things without success, so replaced the USB stick this morning, and so far (only a few hours in) that appears to have fixed the issue... The replaced USB stick was the original I got with the hardware something over 8 years back. Nigel.

2 1

Link-Local ICMP messages for Atlas probe
by Daryl Morse 03 Sep '23

03 Sep '23

I used WireShark on the WAN interface and I can confirm that the messages are all ping requests. Further, I can confirm that all of the addresses have been mangled. They are logged as fe80:5::, but the correct addresses are fe80::. I created a bug report. -----Original Message----- From: Michel Stam <mstam(a)ripe.net> Hi Daryl, Can't say I've seen it before, can the firewall be a bit too strict? I read ICMP messages, but I don't see this in the log you post. Do you have any idea what sort of ICMP messages? Regards, Michel

2 1

Link-Local ICMP messages for Atlas probe
by Daryl Morse 18 Aug '23

18 Aug '23

I've been hosting an Atlas probe since February 2019. I have native dual-stack gigabit fibre internet service and my router is pfSense. Recently, I noticed that there are hundreds of messages in the log of the router like the following: Aug 12 22:38:54 kernel cannot forward src fe80:5::1cce:5fff:fe02:61b6, dst 2001:569:585f:b00:1:b3ff:fedd:9f24, nxt 58, rcvif hn0, outif hn1 Aug 12 22:36:06 kernel cannot forward src fe80:5::e65d:370f:fc45:b5ba, dst 2001:569:585f:b00:1:b3ff:fedd:9f24, nxt 58, rcvif hn0, outif hn1 Aug 12 22:11:31 kernel cannot forward src fe80:5::3c01:20ff:fee5:f601, dst 2001:569:585f:b00:1:b3ff:fedd:9f24, nxt 58, rcvif hn0, outif hn1 Aug 12 17:45:08 kernel cannot forward src fe80:5::2a0:a50f:fcdb:db7c, dst 2001:569:585f:b00:1:b3ff:fedd:9f24, nxt 58, rcvif hn0, outif hn1 Aug 12 15:47:09 kernel cannot forward src fe80:5::2a0:a50f:fcb9:c28e, dst 2001:569:585f:b00:1:b3ff:fedd:9f24, nxt 58, rcvif hn0, outif hn1 Aug 12 08:13:04 kernel cannot forward src fe80:5::2a0:a50f:fc8a:8134, dst 2001:569:585f:b00:1:b3ff:fedd:9f24, nxt 58, rcvif hn0, outif hn1 Aug 12 06:55:33 kernel cannot forward src fe80:5::bac2:530f:fc39:164a, dst 2001:569:585f:b00:1:b3ff:fedd:9f24, nxt 58, rcvif hn0, outif hn1 Aug 12 03:39:05 kernel cannot forward src fe80:5::2a0:a50f:fc8a:85c0, dst 2001:569:585f:b00:1:b3ff:fedd:9f24, nxt 58, rcvif hn0, outif hn1 Aug 12 01:17:54 kernel cannot forward src fe80:5::e6fc:820f:fcea:2016, dst 2001:569:585f:b00:1:b3ff:fedd:9f24, nxt 58, rcvif hn0, outif hn1 Aug 12 00:55:09 kernel cannot forward src fe80:5::ee9e:cd0f:fc0d:79d4, dst 2001:569:585f:b00:1:b3ff:fedd:9f24, nxt 58, rcvif hn0, outif hn1 Aug 11 15:47:11 kernel cannot forward src fe80:5::4271:830f:fce5:7fa, dst 2001:569:585f:b00:1:b3ff:fedd:9f24, nxt 58, rcvif hn0, outif hn1 Aug 11 15:25:42 kernel cannot forward src fe80:5::bac2:530f:fcd4:fdd2, dst 2001:569:585f:b00:1:b3ff:fedd:9f24, nxt 58, rcvif hn0, outif hn1 Aug 11 07:33:53 kernel cannot forward src fe80:5::cd08:c204:cc63:2d32, dst 2001:569:585f:b00:1:b3ff:fedd:9f24, nxt 58, rcvif hn0, outif hn1 Aug 11 06:17:19 kernel cannot forward src fe80:5::fe33:420f:fcdc:5932, dst 2001:569:585f:b00:1:b3ff:fedd:9f24, nxt 58, rcvif hn0, outif hn1 Aug 11 04:49:00 kernel cannot forward src fe80:5::7e25:860f:fc44:6742, dst 2001:569:585f:b00:1:b3ff:fedd:9f24, nxt 58, rcvif hn0, outif hn1 Aug 10 22:41:25 kernel cannot forward src fe80:5::9ca0:15ff:fe87:842e, dst 2001:569:585f:b00:1:b3ff:fedd:9f24, nxt 58, rcvif hn0, outif hn1 Aug 10 14:38:59 kernel cannot forward src fe80:5::c80a:daff:fe92:b8b7, dst 2001:569:585f:b00:1:b3ff:fedd:9f24, nxt 58, rcvif hn0, outif hn1 Aug 10 10:55:07 kernel cannot forward src fe80:5::2a0:a50f:fc8a:6ea0, dst 2001:569:585f:b00:1:b3ff:fedd:9f24, nxt 58, rcvif hn0, outif hn1 Aug 10 08:57:19 kernel cannot forward src fe80:5::46aa:500f:fceb:ad66, dst 2001:569:585f:b00:1:b3ff:fedd:9f24, nxt 58, rcvif hn0, outif hn1 Aug 10 05:47:09 kernel cannot forward src fe80:5::b68a:5f0f:fcb2:1040, dst 2001:569:585f:b00:1:b3ff:fedd:9f24, nxt 58, rcvif hn0, outif hn1 Aug 10 03:24:58 kernel cannot forward src fe80:5::2a0:a50f:fcb6:5ea2, dst 2001:569:585f:b00:1:b3ff:fedd:9f24, nxt 58, rcvif hn0, outif hn1 Aug 10 03:08:55 kernel cannot forward src fe80:5::2a0:a50f:fc90:9d4, dst 2001:569:585f:b00:1:b3ff:fedd:9f24, nxt 58, rcvif hn0, outif hn1 Aug 10 00:17:07 kernel cannot forward src fe80:5::e65d:370f:fc44:15ba, dst 2001:569:585f:b00:1:b3ff:fedd:9f24, nxt 58, rcvif hn0, outif hn1 Aug 10 00:07:07 kernel cannot forward src fe80:5::2a0:a50f:fcb7:7c, dst 2001:569:585f:b00:1:b3ff:fedd:9f24, nxt 58, rcvif hn0, outif hn1 The messages occur in groups of three, spaced a few seconds apart. All of the messages start with fe80:5. Even if I strip off the "5", none of them seem to convert into MAC addresses, so I can't use that to figure out what type of device is pinging the probe. There are no entries in the NDP table corresponding to these messages. I have no idea how long this has been happening. I only noticed it when I was setting up a new server to host pfsense. My probe is RIPE-Atlas-Probe-52209. I'm interested to know if anyone else has experienced this.

5 9

repeating v2 probe usb failure
by Randy Bush 16 Aug '23

16 Aug '23

probe 25898 had a usb failure. i did the unplug usb, power cycle, wait, replug usb. it worked for most of a day and then failed again. rinse repeat. oops, this last time, it has yet to return. can i just order a usb off the net and replace it? or do i just replace the unit? randy

5 6

Probe with ever changing upstreams/ASs?
by Carsten Schiefner 04 Aug '23

04 Aug '23

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.

3 3

System tag
by Ernst J. Oud 04 Aug '23

04 Aug '23

I noticed that the system tag “IPv4 stable 1d” is gone from my probe at: https://atlas.ripe.net/probes/1005104/ I use that tag as a criteria to select active orobes for measurements. But I noticed that my own probe was not included in my measurements. Which is weird since my probe has been online for 2.5 days (normally it is more stable, but my ISP had a small downtime). So my question is what triggers this tag? The tag is self explanatory but what does “stable” mean? Regards, Ernst J. Oud

3 3

Re: [atlas] Probe with ever changing upstreams/ASs?
by Ponikierski, Grzegorz 03 Aug '23

03 Aug '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<mailto:ripe-atlas@ripe.net> https://urldefense.com/v3/__https://lists.ripe.net/mailman/listinfo/ripe-at…<https://urldefense.com/v3/__https:/lists.ripe.net/mailman/listinfo/ripe-atl…>

1 0

Requesting Credits for Research
by Alex Gamero-Garrido 29 Jul '23

29 Jul '23

Hi folks, My name is Alexander Gamero-Garrido and I'm a 5th year PhD student at CAIDA, UC San Diego. We're soon launching a large traceroute campaign for research and could use your generous donation of credits. We'll need about 150 million credits, but any partial amount that gets us closer to that goal is welcome and greatly appreciated. My account is agamerog at eng.ucsd.edu Thank you, Alex -- *Alex Gamero-Garrido* *PhD Student, Computer Science* Web: cseweb.ucsd.edu/~agamerog Center for Applied Internet Data Analysis (CAIDA) San Diego Supercomputer Center UC San Diego Pronouns: He/Him/His <https://inboxwhenready.org/?utm_campaign=signature&utm_medium=email&utm_sou…> I'm using Inbox When Ready <https://inboxwhenready.org/?utm_campaign=signature&utm_medium=email&utm_sou…> to protect my focus.

13 15

Re: [atlas] RIPE Atlas Virtual Anchor Registration for DCS1 (sg-sin-as37989)
by Sanjeev Gupta 28 Jul '23

28 Jul '23

Hi, I am trying to install the virtual anchor of the ISO. Unfortunately, my experience with Unix went directly from Sun to Debian in the late 90s, so I am not sure of the intricacies of RHEL anaconda What (and in what format) do I answer here: 1. IPv4 address: 203.123.48.20 2. IPv4 Netmask: I tried 255.255.255.224, which it seemed not to like, so I tried /27, and then 27. 3. IPv4 gateway: 203.123.48.6 4. IPv6 address: 2405:fc00::20 (it keeps failing, should I enclose this in [] )? 5. IPv4 Netmask: I tried /64, and then 64 6. IPv4 gateway: 2405:fc00::6 Now it fails with: <snip>freedektop.NetworkManager.Settings.Connection.MissingPropert: ipv4.addresses: this propery cannot be empty for 'method=manual' And how do I backspace in the installer? Neither BKSP nor ^H seem to work. Thanks, -- Sanjeev Gupta +65 98551208 http://www.linkedin.com/in/ghane On Thu, 27 Jul 2023 at 22:22, RIPE Atlas <no-reply(a)ripe.net> wrote: > Dear Sanjeev Gupta, > > Thank you for registering the technical information for your RIPE Atlas > virtual anchor! > > Your FQDN is: sg-sin-as37989.anchors.atlas.ripe.net > > You will need now to setup the Virtual Machine according to these > instructions: (https://atlas.ripe.net/docs/anchor-installation-vm/) > > It is important that once you have setup the virtual machine, you log in > to your RIPE Atlas account, go to the "My Atlas" menu and then "Anchors", > and check the boxes “Software is installed” and "Anchor is connected to the > network" so we are notified and can begin the tests. Please note that your > anchor will not be fully activated until we have finished these internal > tests. > > We will notify you once we have finished testing and your virtual anchor > is ready to use. > > If you have any questions, please do not hesitate to contact us at > atlas(a)ripe.net > > You registered the following details: > > IPv4 address: 203.123.48.20 > IPv4 ASN: 37989 > > IPv6 address: 2405:fc00::20 > IPv6 ASN: 37989 > > Kind regards, > > RIPE Atlas Team >

2 1

Easy way to view DNS results?
by Micha Bailey 27 Jul '23

27 Jul '23

Hi, I’m wondering if I’m missing something - I ran a DNS measurement with 110 probes, and the results are in, but the site UI seems to only show the result status and time elapsed until response, but not the results themselves. Looking at the JSON from the result endpoint I’m seeing that it seems to return the raw binary response - is there a particular reason it can’t be parsed and displayed in a more human-readable format? I know there are libraries and tools that do result parsing, but being on mobile at the moment (and often) means those are somewhat less accessible as far as I’m aware.

6 6

Re: [atlas] DoH and DoT measurements
by Ponikierski, Grzegorz 26 Jul '23

26 Jul '23

Indeed “tls” flag seems to work. Thanks! After first try with DoT providers like one.one.one.one or dns.google I have additional question. When exactly FQDN from “target” is resolved to IP? Is RIPE Atlas resolve domain to IP only once during measurements creation or is each probe resolve domain to IP individually? It’s important details for me because I will work with FQDN that will resolve do different IP depending on user location so if it is resolved only once by RIPE Atlas system then probes will be using sub-optimal IPs to run tests. Regards, Grzegorz From: Michel Stam <mstam(a)ripe.net> Date: Wednesday, 26 July 2023 at 17:13 To: "Ponikierski, Grzegorz" <gponikie(a)akamai.com> Subject: Re: [atlas] DoH and DoT measurements Hey Grzegorz, It’s a bit hidden, but in the measurement definition I think the key ’tis’ needs to be set to the boolean value ’true’. That should enable DNS over TLS. Cheers, Michel On 26 Jul 2023, at 17:09, Ponikierski, Grzegorz <gponikie(a)akamai.com> wrote: I have reviewed API Manual and Reference but I don’t see anything about DoH or DoT. Maybe I have overlooked something? Regards, Grzegorz From: Michel Stam <mstam(a)ripe.net<mailto:mstam@ripe.net>> Date: Wednesday, 26 July 2023 at 15:30 To: "Ponikierski, Grzegorz" <gponikie(a)akamai.com<mailto:gponikie@akamai.com>> Cc: "ripe-atlas(a)ripe.net<mailto:ripe-atlas@ripe.net>" <ripe-atlas(a)ripe.net<mailto:ripe-atlas@ripe.net>> Subject: Re: [atlas] DoH and DoT measurements Hello Gzzegorz, If I saw correctly DNS over TLS should be possible. Some initial steps have been taken to implement DNS over HTTP(S) but such is not available yet. You will probably have to use the API to schedule one, though RIPE Atlas docs | RIPE Atlas Documentation | Docs<https://urldefense.com/v3/__https:/atlas.ripe.net/docs/__;!!GjvTz_vk!UIWbNO…> atlas.ripe.net<https://urldefense.com/v3/__https:/atlas.ripe.net/docs/__;!!GjvTz_vk!UIWbNO…> <image001.png><https://urldefense.com/v3/__https:/atlas.ripe.net/docs/__;!!GjvTz_vk!UIWbNO…> Hope this helps, Regards, Michel On 26 Jul 2023, at 15:09, Ponikierski, Grzegorz via ripe-atlas <ripe-atlas(a)ripe.net<mailto:ripe-atlas@ripe.net>> wrote: Hi! Is it possible to run DNS over HTTPS and DNS over TLS measurements with RIPE Atlas? Regards, Grzegorz -- ripe-atlas mailing list ripe-atlas(a)ripe.net<mailto:ripe-atlas@ripe.net> https://lists.ripe.net/mailman/listinfo/ripe-atlas<https://urldefense.com/v3/__https:/lists.ripe.net/mailman/listinfo/ripe-atl…>

2 2

DoH and DoT measurements
by Ponikierski, Grzegorz 26 Jul '23

26 Jul '23

Hi! Is it possible to run DNS over HTTPS and DNS over TLS measurements with RIPE Atlas? Regards, Grzegorz

2 2

Issues downloading large result files
by Ana 21 Jul '23

21 Jul '23

Hi everyone, I'm seeing something very strange when trying to download the result files for some large measurements. The download is a different size each time (sometimes 1.4GB, then 3.2GB, then back to 1 GB again) and checking the end of the file I can always see it's not complete as it stops in the middle of a measurement, closing brackets aren't there etc. I guess this is because of the size of the file, not sure if there's some sort of limit on RIPE Atlas? If anyone here has seen anything like this or has any advice on how to fully download the result that would be much appreciated! Thank you, Ana

3 2

Re: [atlas] RIPE Atlas Virtual Anchor Registration for Angola Cables (ao-lad-as37468)
by Inacio Jose 17 Jul '23

17 Jul '23

1 0

Looking for RIPE Atlas credits
by Ioana Alexandrina Livadariu 17 Jul '23

17 Jul '23

Hello all, My name is Ioana Livadariu and I am a researcher at SimulaMet in Norway working on IP geolocation. I want to run a measurement campaign over RIPE Atlas which requires about 1M RIPE Atlas credits. If anybody can help me by sharing credits I would appreciate it a lot! My email for transfer is: ioana(at)simula.no Thank you, Ioana Livadariu

3 2

Credit request
by Ana Custura 13 Jul '23

13 Jul '23

Hi everyone, I would like to schedule some experiments to look at the prevalence and types of load-balancing in v4 and v6 networks. Running traceroutes with 32 paris repetitions on many probes unfortunately burns very quickly through credits. If you have some to spare and can donate to my account it would be much appreciated! Thank you, Ana

10 10

RIPE87: CfP, RACI & Fellowship Grants
by Vesna Manojlovic 13 Jul '23

13 Jul '23

Dear colleagues, RIPE 87 will be held in Rome, from 29 November to 2 December 2023: https://ripe87.ripe.net/ ----------- CFP ----------- Please propose a talk or a workshop at https://ripe87.ripe.net/cfp/ RIPE 87 will be a hybrid meeting, so both in-person and remote presentations are encouraged and will be accepted. ----------- Travel Grants ----------- The RIPE NCC is accepting applications for RIPE Fellowship and academics: travel grants are available for selected candidates. *The application deadline is Tuesday, 11 September 2023.* ----------- RACI ----------- RIPE Academic Cooperation Initiative (RACI) is supporting talented academics in the field of Internet technology. Successful applicants receive complimentary tickets, accommodation and travel to the meetings and the opportunity to present their research. To apply, submit a short abstract and draft slides via: https://www.ripe.net/participate/forms/apply/raci-application-form-2023/ More information: https://www.ripe.net/raci Subscribe to the RACI list: https://www.ripe.net/raci/mailing-list ----------- RIPE Fellowship ----------- Having participants with diverse backgrounds, expertise, opinions and experiences enriches the RIPE community. With the RIPE Fellowship, we aim to create opportunities for individuals from underrepresented regions, minority backgrounds, or others who would otherwise be unable to attend without funding, to participate in the RIPE Meetings. The RIPE Fellowship covers the cost of a meeting ticket, travel and accommodation for successful candidates in the RIPE NCC service region. Apply: https://www.ripe.net/participate/forms/apply/ripe-87-fellowship/ More information: https://www.ripe.net/fellowship ----------- We encourage our long-standing community members to share this announcement with others who could benefit from these opportunities. ----------- Warm regards, Vesna Manojlovic -- Senior Community Builder, RIPE NCC https://labs.ripe.net/author/becha/

1 1

Re: [atlas] Your Probe shipped
by Inacio Jose 11 Jul '23

11 Jul '23

2 1

credit transfer - 2 issues
by Paul Emmons 11 Jul '23

11 Jul '23

Hello all. First off, does the standing order for transferring credits form work? I have tried it a few times with no success on chrome and firefox. I submit it and nothing happens. And I can't seem to get a transfer done via a curl method - just get a invalid method response. A sample of the code we were trying is: curl -H "Content-Type: application/json" -H "Accept: application/json" -X POST -d '{ "amount":"1999999" , "recipient":"paul@somedomain" }' https://atlas.ripe.net/api/v2/credits/transfer/?key=a-real-key Thanks Paul

2 1

Accuracy of “Consumption Delay”
by Ernst J. Oud 01 Jul '23

01 Jul '23

L.S. To feed to the discussion… currently the “Consumption Delay” indicator is green while results of a new measurement still take a long time (half an hour or more) to be reported fully in the web interface. So this indicator cannot be fully relied on it seems. Met vriendelijke groet / Regards, Ernst J. Oud

1 0

Delays in backend…
by Ernst J. Oud 01 Jul '23

01 Jul '23

Hi, Measurements stream fine in Magellan, but results only show up in the web interface after - in extreme cases - hours. The RIPE status info says: Resolved This incident has been resolved. Posted 1 day ago. Jun 29, 2023 - 10:11 UTC Investigating We are experiencing issues with the RIPE Atlas backend and currently are investigating this issue. Posted 1 day ago. Jun 29, 2023 - 08:55 UTC But clearly this has not been resolved! Regards, Ernst J. Oud

2 3

RIPE Atlas Quarterly Planning Q3 2023
by Robert Kisteleki 28 Jun '23

28 Jun '23

Dear colleagues, We have published our next quarterly plans for RIPE Atlas on our website: https://www.ripe.net/support/documentation/quarterly-planning/ripe-atlas This quarter, we'll continue discussing the five proposals for changing the RIPE Atlas behaviour and start working on renewing the big data backend. If you have any input on our plans or want to let us know what you would like to see us work on, please let us know. Kind regards, Robert Kisteleki RIPE NCC

1 0

Magellan
by Ernst J. Oud 26 Jun '23

26 Jun '23

Hi, Perhaps someone can help me. I use Magellan to create a measurement using connected probes on AS15435. First I search for probes using Magellan and then I supply the ID’s returned of those probes reported as “connected” when creating the measurement. I don’t want to wait for the stream to time-out so I use the “stream-limit” parameter, equal to the number of supplied connected probes. So when that number of connected probes have supplied data the streaming is complete. However, it appears that probes are reported as connected by Magellan but do not supply data when specified for a measurement, for instance probe 2565. That probe is Reported by Magellan as connected but when I use it in a measurement it does not supply data. Thus streaming will only time-out and does not stop not when spevified connected probes have supplied data. Apparantly “connected” does not imply “can be used in a measurement”. How can I supply probe ID’s in a “create measurement” command using Magellan knowing for sure that these probes will supply data? Regards, Ernst J. Oud

2 2

Recovered probe v3
by Renny Leal 26 Jun '23

26 Jun '23

Hi folks I’ve recovered one V3 probe but sadly the person who got it flashed the tp-link original firmware to the device. Is there any way to get the ripe atlas firmware back to it? Thanks in advance Enviado desde Correo<https://go.microsoft.com/fwlink/?LinkId=550986> para Windows

2 1

Fw: Action Required: RIPE Atlas Probe 52974 and RIPE NCC Days Sofia invitation
by Endre Szabo 21 Jun '23

21 Jun '23

Hi folks, I've got a probe running at a very remote site. Since the energy prices were skyrocketing with the crisis here in Eastern Europe, the probe does not have 7x24 power anymore. It is down for 10-ish hours a weekday. It's been running like this for months now. Suddenly, I've just got this mail below about my probe. The probe is online every day and was online today as well. Does this mail mean that RIPE is unsatisfied with my uptime, and I must return the probe? Or is it some monitoring needing some tuning? --Endre ----- Forwarded message from RIPE Atlas <no-reply(a)ripe.net> ----- From: RIPE Atlas <no-reply(a)ripe.net> Subject: Action Required: RIPE Atlas Probe 52974 and RIPE NCC Days Sofia invitation Date: Tue, 20 Jun 2023 13:01:05 -0000 Dear Endre Szabo, We hope this email finds you well. We noticed that your probe with ID 52974 has been disconnected for some time now, and you have probably received reminders from our system asking you to reconnect it. We would like to request you to please either reconnect the probe, or if that is not possible, to return it to us to be refurbished. There is a long waiting list of people keen to receive new probes, and because of global component shortages, we have a very limited number available. 1. You can check your probe using this link below. https://atlas.ripe.net/probes/52974/#tab-status If your probe is already online, you can stop reading here! 2. If you need to troubleshoot a disconnected probe, you can take a look at our tutorials on YouTube, or write to us asking for assistance. https://www.youtube.com/watch?v=BGj1MDIclDQ 3. If the probe is beyond repair, please go here: https://atlas.ripe.net/probes/52974 and click on the "Write-off" button at the bottom of the page. This will allow you to choose a reason for writing off the probe. This will clear the probe host name, and you will no longer receive any more reminders from us about the probe. 4. If you no longer wish to host the probe, please follow step 3 and then send the probe back to us. We will refurbish and redistribute it. Please use this address for shipping: RIPE NCC P.O. Box 10096 1001 EB Amsterdam The Netherlands ===== RIPE NCC Days Sofia, Bulgaria And finally, join us at RIPE NCC Days Sofia, Bulgaria on 27-28 June 2023! This free event provides a unique opportunity for network operators and technical staff to share knowledge and experiences. Don't miss out – register now at https://www.ripe.net/participate/meetings/regional-meetings/ripe-ncc-days-s… . We look forward to seeing you there! ===== Thank you for continuing to support RIPE Atlas. Best regards, The RIPE Atlas Team ----- End forwarded message -----

2 2

Fw: Action Required: RIPE Atlas Probe 52974 and RIPE NCC Days Sofia invitation
by Endre Szabo 20 Jun '23

20 Jun '23

Hi folks, I've got a probe running at a very remote site. Since the energy prices were skyrocketing with the crisis here in Eastern Europe, the probe does not have 7x24 power anymore. It is down for 10-ish hours a weekday. It's been running like this for months now. Suddenly, I've just got this mail below about my probe. The probe is online every day and was online today as well. Does this mail mean that RIPE is unsatisfied with my uptime, and I must return the probe? Or is it some monitoring needing some tuning? --Endre ----- Forwarded message from RIPE Atlas <no-reply(a)ripe.net> ----- From: RIPE Atlas <no-reply(a)ripe.net> Subject: Action Required: RIPE Atlas Probe 52974 and RIPE NCC Days Sofia invitation Date: Tue, 20 Jun 2023 13:01:05 -0000 Dear Endre Szabo, We hope this email finds you well. We noticed that your probe with ID 52974 has been disconnected for some time now, and you have probably received reminders from our system asking you to reconnect it. We would like to request you to please either reconnect the probe, or if that is not possible, to return it to us to be refurbished. There is a long waiting list of people keen to receive new probes, and because of global component shortages, we have a very limited number available. 1. You can check your probe using this link below. https://atlas.ripe.net/probes/52974/#tab-status If your probe is already online, you can stop reading here! 2. If you need to troubleshoot a disconnected probe, you can take a look at our tutorials on YouTube, or write to us asking for assistance. https://www.youtube.com/watch?v=BGj1MDIclDQ 3. If the probe is beyond repair, please go here: https://atlas.ripe.net/probes/52974 and click on the "Write-off" button at the bottom of the page. This will allow you to choose a reason for writing off the probe. This will clear the probe host name, and you will no longer receive any more reminders from us about the probe. 4. If you no longer wish to host the probe, please follow step 3 and then send the probe back to us. We will refurbish and redistribute it. Please use this address for shipping: RIPE NCC P.O. Box 10096 1001 EB Amsterdam The Netherlands ===== RIPE NCC Days Sofia, Bulgaria And finally, join us at RIPE NCC Days Sofia, Bulgaria on 27-28 June 2023! This free event provides a unique opportunity for network operators and technical staff to share knowledge and experiences. Don't miss out – register now at https://www.ripe.net/participate/meetings/regional-meetings/ripe-ncc-days-s… . We look forward to seeing you there! ===== Thank you for continuing to support RIPE Atlas. Best regards, The RIPE Atlas Team ----- End forwarded message -----

1 1

Can <contact@streamyard.com> please be unsubscribed?
by Carsten Schiefner 17 Jun '23

17 Jun '23

To whom it may concern… Thank you, -C.

3 2

Vergessen Sie nicht Ihre StreamYard-Einladung!
by StreamYard 17 Jun '23

17 Jun '23

StreamYard Inc. ( https://u7212249.ct.sendgrid.net/ls/click?upn=Ef-2BTvyZXeR9MIWcIdAYELFJPNYC… )

1 0

Sie wurden zu StreamYard eingeladen
by StreamYard 10 Jun '23

10 Jun '23

StreamYard Inc. ( https://u7212249.ct.sendgrid.net/ls/click?upn=Ef-2BTvyZXeR9MIWcIdAYELFJPNYC… )

1 0

upgrading an original soft probe
by Randy Bush 08 Jun '23

08 Jun '23

i have a probe, 1000004, on a deb 10 vm that was installed in the rotterdam hackathon. the detritus looks as if it was built using a deb install of atlasswprobe-5000-1.deb. two days ago, it stopped working in some way; i have not pursued, figuring i was dealing with an antique. is there a path to make it current? randy

4 9

Re: [atlas] credit request
by Michael Rabinovich 06 Jun '23

06 Jun '23

Many thanks! As I mentioned, I did get all the credits requested, but I am grateful to have them as it will allow us extra flexibility to do some exploratory measurements. Cheers, —Misha > On Jun 4, 2023, at 6:53 PM, DeuZa <proton(a)deuza.net> wrote: > > Sent 181 000 000 credits > > Sent from Proton Mail for iOS > > > Le mer. 24 mai 2023 à 17:29, Michael Rabinovich <michael.rabinovich(a)case.edu <mailto:Le mer. 24 mai 2023 %C3%A0 17:29, Michael Rabinovich <<a href=>> a écrit : >> >> Folks, >> >> As I posted couple months ago, we deployed and made available the instrumentation for longitudinal comparison of the performance implications of DNS resolver platforms, including ISP-provided and some influential publicly available resolvers ( https://dns-web-portal.netlify.app/) This work — and Nick Kernan’s MS thesis — was enabled by a generous donation of credits several years ago from the RIPE Atlas community — thanks a lot! Now to keep this measurement going requires ~20M credits per month. I’d like to assemble ~250M credits so we could keep this service up for a year. By then we should be able to see if it’s proved to be valued by the community and whether and how to keep it going beyond this time horizon. Would you please donate to my account what you can? >> >> Many thanks in advance! >> —Misha > <publicKey - proton(a)deuza.net - 0x714FB45F.asc>

1 0

credit request
by Michael Rabinovich 25 May '23

25 May '23

Folks, As I posted couple months ago, we deployed and made available the instrumentation for longitudinal comparison of the performance implications of DNS resolver platforms, including ISP-provided and some influential publicly available resolvers ( https://dns-web-portal.netlify.app/) This work — and Nick Kernan’s MS thesis — was enabled by a generous donation of credits several years ago from the RIPE Atlas community — thanks a lot! Now to keep this measurement going requires ~20M credits per month. I’d like to assemble ~250M credits so we could keep this service up for a year. By then we should be able to see if it’s proved to be valued by the community and whether and how to keep it going beyond this time horizon. Would you please donate to my account what you can? Many thanks in advance! —Misha

9 15

Probe DHCPv6 support
by Aleksi Pirttimaa 19 May '23

19 May '23

Hi! I recently received my v4 probe and I'm very happy with it. But unfortunately it doesn't support DHCPv6. I present a practical reason for implementing a DHCPv6 client on the probe. You see, my ISP doesn't send router advertisements with the prefix for stateless autoconfiguration set, and instead DHCPv6 must be used. I believe their decision could have something to do with the fact that the regulating body here requires ISP's to prevent IP address spoofing in consumer plans. And to meet that requirement my ISP may be using a feature similar to Cisco's IP source guard, where switch ports and/or mac addresses are passively associated to leased ip's or prefixes, breaking SLAAC. Unfortunately they hate letting consumers talk with their engineers so it's difficult to speculate this further. For now, I've put a stateful firewall appliance in front of the probe which provides SLAAC, it works just fine. Do you think a DHCPv6 client should be implemented?

8 13

Measurement suggestions for new deployments.
by Gerardo Huerta Robles 18 May '23

18 May '23

Hello all, I'm a newbie with RIPE ATLAS Probes, We are currently working on deploying a new Probe network in Nicaragua as the first step for a measurement project. The second step will be to capture statistics of traffic to the internet, but we are not clear what kind of targets are the most relevant for internet statistics. I would like to ask you for suggestions of targets, what kind of public servers are relevant for user internet traffic? We are thinking of DNS servers like 8.8.8.8 or some public HTTP web pages like the government or social media like Facebook, youtube and so on. But what do you think? Do you have some advice? The project is intended to obtain the first statistics about internet traffic and make it public using RIPE Probes and schedule measurements. If you have some advice please let me know, Thank you. Regards

1 0

RIPE Anchor updates?
by John Howard 16 May '23

16 May '23

Hi folks, Proton hosts 3 RIPE Anchors (7120, 6847, 6854) and during routine vulnerability scanning we identified these appliances running nginx 1.20.1, which is potentially vulnerable to two CVEs (CVE-2022-41741 and CVE-2022-41742). Given the mp4 module pre-req, I doubt they are vulnerable in practice, but this highlighted that the nginx 1.20 train was deprecated 11 months ago, and 1.23/1.24 are the currently active releases. I note the last probe firmware update 5080 (which we run already) from Nov/22 disabled auto updates on the appliances, so I assume there will be regular updates coming from RIPE going forward instead? Thanks John -- John Howard Head of Network Infrastructure Proton AG Sent with Proton Mail secure email.

2 3

Request RIPE Atlas Credit for Research
by 卫蕴泽 28 Apr '23

28 Apr '23

Dear all, Greetings! I'm a senior student at Tsinghua University, China. Recently I'm working on my graduation project, which is a IP infrastructure mapping research that requires large-scale network measurement via RIPE Atlas to verify my method. However, a simple traceroute with 6 probes need 10K+ credits. As a new user I don't have any credit to proceed, and I've no time to earn them by myself. So I'm here to ask for help. Is it possible for anyone generous enough to offer me some RIPE Atlas credits (like, 10M)? My account at RIPE NCC is fenglan.chn(a)gmail.com, my education email is weiyz19(a)mails.tsinghua.edu.cn and my student ID is 2019011285. Many thanks for your help! Sincerely, Yunze Wei

6 6

a link for comparing DNS resolvers
by Michael Rabinovich 04 Apr '23

04 Apr '23

Folks, FYI, Nick Kernan, my Masters student, has deployed a web portal that facilitates the comparison between various DNS resolvers, including ISP-provided and some influential publicly available resolvers (Google’s public DNS, OpenDNS, Quad9, and Cloudflare). The comparison is based on two factors: the latency of DNS resolutions and the latency of TCP handshake with the CDN edge server selected through a given resolver. The results are based on recurrent monthly measurements from RIPE Atlas probes that have both IPv4 and v6 connectivity, have an ISP-provided resolver available for comparison, and which meet certain requirements regarding probe versions and reliability. You can specify the desired month of measurement, a region of interest, and the CDNs to analyze. You can access Nick’s portal through https://dns-web-portal.netlify.app/ <https://dns-web-portal.netlify.app/> The details of the methodology are in Nick’s thesis, which awaits some copyright permissions before being made publicly available. In the meantime, Nick (cc’ed) and I would be happy to answer any questions. Regards, —Misha Rabinovich

4 4

RIPE Atlas Quarterly Planning Q2 2023
by Robert Kisteleki 30 Mar '23

30 Mar '23

Dear colleagues, We’ve now published our quarterly planning for RIPE Atlas. These are available at: https://www.ripe.net/support/documentation/quarterly-planning/ripe-atlas This quarter, we'll continue the discussion on five proposals for changing RIPE Atlas behaviour and work on restructuring and renewing pages of the user interface. If you have any input on our plans or want to let us know what you would like to see us work on, please let us know. Kind regards, Robert Kisteleki RIPE NCC

1 0

Planned Maintenance: RIPE Atlas streaming API, 28-03-2023, 9.00am - 10.00am UTC
by Marco Giuliani 27 Mar '23

27 Mar '23

Hello, We will carry out planned maintenance on the RIPE Atlas streaming API. During this time, existing HTTP sessions will be briefly interrupted. Start: March, 28th, 2023 - 9.00am UTC End: March, 28th, 2023 - 10.00am UTC Kind regards, Marco Giuliani RIPE NCC

1 0

Join the DNS Hackathon on 20 and 21 May in Rotterdam (weekend before RIPE 86)
by Vesna Manojlovic 21 Mar '23

21 Mar '23

Dear colleagues, I am pleased to invite you to participate in the DNS hackathon that will take place the weekend before RIPE 86 at Ahoy in Rotterdam, on Saturday 20 May and Sunday 21 May 2023. The hackathon is organised by DNS-OARC, Netnod and the RIPE NCC and offers projects based on three challenges: DNS &... Sustainability Security (and privacy) Sovereignty You can also bring your own idea or project. To participate, apply here: https://www.ripe.net/participate/forms/apply/dns-hackathon-2023/ (first deadline is on Thursday, 23 March 2023) Read more at: https://www.netnod.se/join-the-dns-hackathon-2023 Feel free to share this invitation with your communities. Regards, Vesna Manojlovic -- Senior Community Builder, RIPE NCC https://labs.ripe.net/author/becha/

1 0

HTTP measurement proposals [CDN-HTTP] [GENERIC-HTTP] [PEERING-HTTP]
by Ethan Katz-Bassett 06 Mar '23

06 Mar '23

Hi Robert, all: I was considering emailing about the possibility of HTTP measurements to our PEERING <https://peering.ee.columbia.edu/> testbed when I stumbled on the five proposals that Robert posted in December. I want to express my strong support for the two HTTP proposals. Hourly [CDN-HTTP] would be great (eventually with HTTPS support). ([STARTTLS] also sounds good, but I haven't thought deeply about it, and [ONLY-PUBLIC] sounds good unless it costs RIPE Atlas support / probe hosts) I was wondering about the feasibility of allowing HTTP measurements towards PEERING experiments (meaning, towards our address space announced from an experiment via our routers). Is that something that you might be open to supporting? This came to mind because we are in the process of onboarding PEERING to some bring-your-own-prefix services offered by CDNs and cloud providers, and so an increasing number of PEERING experiments are about content delivery/cloud hosting, and it would be great if RIPE Atlas could act as measurement clients to provide widespread vantage points. One hands-off option that comes to mind is to set them up similar to the proposal for CDN-HTTP, where probes will regularly fetch an object at a fixed URL, say http://ripeatlas.ee.columbia.edu/testobject. Normally, that could resolve to our project webserver, which is hosted in AWS. When an experiment needs this HTTP capability (all experiments undergo review by at least 2 people for safety, and we enable only the capabilities they request and need, following the principle of least privilege), we could instead redirect it to a PEERING address allocated to the project that would host the same test object but that would be announced from cloud/CDN/PEERING sites however the experiment had configured. Alternatively, it could be a measurement available to approved accounts, and we could pass on which experiments are approved, or perhaps available to all accounts. We have fixed address space, if you have a way to whitelist. We maintain our list of prefixes as RS-PEERING-TESTBED on RIPE's IRR. I believe Johan recently contacted Kevin Vermeulen about talking to us about RIPE Atlas in the context of another one of our projects, so possibly we can have a discussion covering both topics. Thanks for all your work providing the platform -- it's great! Ethan -- http://www.columbia.edu/~ebk2141/

1 0

Errors on Measurement web interface
by ripe＠brite.cz 01 Mar '23

01 Mar '23

Hi team, I see issues with Latencymon, such as https://atlas.ripe.net/measurements/48750273/#latencymon Upon opening it displays message "Server is responding slowly", after a while it displays the default view. But when I expand the time range a bit, or make any change to the view, it will show nothing and after a while displays message "It is not possible to download data from the API" Tried Firefox and Chrome, same result. The same result when I open only the frame, such as https://atlas.ripe.net/frames/measurements/48750273#latencymon

2 1

Re: [atlas] Measurement question
by Michel Stam 20 Feb '23

20 Feb '23

Hello Roberto, I’ve done the exact same measurement too, using the 3 types of traceroute available (ICMP, UDP and TCP). UDP: (https://atlas.ripe.net/measurements/49826077/#general) TCP: (https://atlas.ripe.net/measurements/49826078/#general) ICMP: (https://atlas.ripe.net/measurements/49826076/#general) The way the traceroute works in Atlas is that if 5 hops have been received without response, the trace skips over to TTL 255 and ends the traceroute. This is what you see with TCP and ICMP. The traceroute stops for lack of response. To prove that, I’ve run the trace again, skipping hops 1-7, for both ICMP and TCP: https://atlas.ripe.net/measurements/49826868/#general https://atlas.ripe.net/measurements/49826959/#general Now for the interesting bits: 100.64.0.0/10 is CGN (Carrier Grade NAT), RFC 6598. Looking at the traceroute differently: Hop 1 (AS16509, Amazon EU West, Amazon-02) Hop 2-7 CGN Hop 8-9 (AS unknown, but between UK and US, IPROU3-ARIN, so Amazon IP routing 3) Hop 10 (AS unknown, but between UK and US, IPROU3-ARIN/ARMP-ARIN, Amazon IP routing) Hop 11-15 CGN Hop 16 (AS unknown, presumably US, IPROU3-ARIN/ARMP-ARIN, I presume Amazon IP routing still) Hop 17-19 CGN Hop 20 (AS13335, Cloudflare US) So it seems like every cloud zone interconnect (amazon Europe west, US, then Cloudflare) transitted goes through a CGN setup. Not sure but I can understand if this confuses some types of traffic. I don’t think there’s anything wrong with your setup, but the results are interesting. I’ve copied a couple of our researchers onto the mail as they may be interested in this as well. Regards, Michel > On 8 Feb 2023, at 11:33, roberto.lucignani(a)caleidos.it wrote: > > Hi Michael, > for example, one measure ID is this one: 49813750 > The result says there are 7 HOPS. > The result of the traceroute made directly on the host is the following one > traceroute to www.madghigno.tech (172.67.221.209), 30 hops max, 60 byte packets > 1 52.56.0.19 24.303 ms 52.56.0.31 9.067 ms 52.56.0.17 29.663 ms > 2 * 100.65.18.192 7.843 ms 100.65.19.176 6.252 ms > 3 100.66.8.254 1.563 ms 100.66.8.146 0.697 ms 100.66.8.168 1.449 ms > 4 100.66.10.138 8.469 ms 100.66.10.14 5.713 ms 100.66.10.6 8.127 ms > 5 100.66.7.77 1.653 ms 100.66.6.173 2.658 ms * > 6 100.66.4.75 2.726 ms 100.66.4.87 2.327 ms 100.66.4.89 1.550 ms > 7 100.65.10.65 0.533 ms 100.65.11.1 0.857 ms 100.65.10.161 8.616 ms > 8 15.230.158.29 2.062 ms 15.230.158.171 5.998 ms 15.230.158.27 1.617 ms > 9 15.230.158.164 1.315 ms 52.94.33.120 2.089 ms 15.230.158.40 1.484 ms > 10 54.239.101.83 1.440 ms 150.222.65.23 1.358 ms 54.239.101.87 1.897 ms > 11 100.91.211.7 1.368 ms 100.91.13.66 1.956 ms 100.91.13.100 5.077 ms > 12 100.91.210.16 1.837 ms 100.100.6.119 1.848 ms 52.93.134.81 2.178 ms > 13 100.100.73.70 2.434 ms 100.91.203.106 4.546 ms 100.100.85.70 1.139 ms > 14 100.91.207.15 1.289 ms * 100.100.72.67 1.767 ms > 15 100.100.2.76 3.616 ms 100.91.201.140 1.955 ms 100.91.205.18 1.744 ms > 16 99.83.89.19 6.820 ms 100.91.201.1 2.454 ms 100.91.201.97 2.415 ms > 17 100.91.211.89 17.823 ms 172.71.176.2 3.200 ms 172.70.160.2 4.450 ms > 18 100.100.6.77 1.805 ms 100.100.6.3 1.943 ms 100.100.6.111 2.005 ms > 19 100.100.80.70 1.980 ms 100.100.76.134 2.679 ms 100.100.69.134 2.081 ms > 20 172.67.221.209 2.799 ms 100.100.89.209 7.318 ms 100.100.89.17 6.869 ms > Since the website is served by cloudflare the route may vary between requests but the are always around 18/20 HOPS > I don’t understand if I0m missing something here. Let me know if you need further details > Regards, > Roberto > From: Michel Stam <mstam(a)ripe.net> > Date: Wednesday, 8 February 2023 at 10:13 > To: roberto.lucignani(a)caleidos.it <roberto.lucignani(a)caleidos.it> > Subject: Re: [atlas] Measurement question > Hello Roberto, > Would you be able to share screenshots/measurement ids so we can have a look? > Regards, > Michel > > > On 8 Feb 2023, at 09:04, roberto.lucignani(a)caleidos.it wrote: > I’m doing some measurement from one of my software probes, the measure is a traceroute to a destination. > The results I get are completely different from what I see doing the same traceroute directly on host where the probe is installed. I configured the measure to sue the DNS resolution on the probe.. > From the Atlas portal I get a traceroute with 7 hops, doing it directly on the host returns 28 hops, for the same destination. > Why this difference ? > Regards, > Roberto > -- > Mail sent with Outlook for Mac > This message contains confidential information and is intended only for the individual named. If you are not the named addressee, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this message by mistake and delete this message from your system. E-mail transmission cannot be guaranteed to be secure or error-free, because information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this message that arise as a result of e-mail transmission. > -- > ripe-atlas mailing list > ripe-atlas(a)ripe.net > https://lists.ripe.net/mailman/listinfo/ripe-atlas

2 4

Offering a v1 probe for adoption in RU
by Roman Mamedov 20 Feb '23

20 Feb '23

Hello, I am offering my probe to someone else within Russia for "adoption" (ownership transfer). Despite being a v1, it still runs well with no downtime. Contact me on Telegram via @romanrm to discuss (in Russian or English), or via E-Mail if you don't have an account. Thanks -- With respect, Roman

1 0

Atlas V5 - Rack-Mounting Solution
by Johannes Schiemer 19 Feb '23

19 Feb '23

Dear all, As I have just received my Atlas V5 Probe and wanted to mount it in my Rack, I've decided to 3d-Print a holder for the probe. I've also decided to share it with all of you in the hopes that some of you might find it useful. This is the link to thingiverse: https://www.thingiverse.com/thing:5864347 Thanks! Greetings, Johannes

1 0

Missing ping and traceroute dumps for 2023-01-23
by Maxime Mouchet 15 Feb '23

15 Feb '23

Hi, I noticed that there is no ping and traceroute dumps for 2023-01-23: https://data-store.ripe.net/datasets/atlas-daily-dumps/2023-01-23/ The other days are fine though. Is there any chance to get these dumps? Or are they just lost? Thanks! Maxime

2 3

Measurement question
by roberto.lucignani＠caleidos.it 08 Feb '23

08 Feb '23

I’m doing some measurement from one of my software probes, the measure is a traceroute to a destination. The results I get are completely different from what I see doing the same traceroute directly on host where the probe is installed. I configured the measure to sue the DNS resolution on the probe.. >From the Atlas portal I get a traceroute with 7 hops, doing it directly on the host returns 28 hops, for the same destination. Why this difference ? Regards, Roberto -- Mail sent with Outlook for Mac This message contains confidential information and is intended only for the individual named. If you are not the named addressee, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this message by mistake and delete this message from your system. E-mail transmission cannot be guaranteed to be secure or error-free, because information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this message that arise as a result of e-mail transmission.

1 0