- ripe-atlas - mailman.ripe.net

New Atlas Measurement Creation Form (BETA)
by Stephen Suess 18 Sep '23

18 Sep '23

Hello Atlas fans, As part of our ongoing User Interface renewal activity we've been working on a redesign of the measurement creation form. Today, we're excited to announce the release of this new form in beta, and we would love your feedback and suggestions as we continue to develop it. Notable improvements include: - A simplified and cleaner user interface. - Client-side functionality, eliminating the need for external libraries, websites, or APIs (except for cost calculations and final submit). - Enhanced performance. - Mobile-friendly design. - Clearer probe selection information. - Presentation of API specification with and without the cURL command. You can find the new form at https://atlas.ripe.net/mform or in the menu under "Measurements -> Create Measurement (BETA)". 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-measurement-form-beta/678 Thanks! Stephen RIPE Atlas UI

1 0

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