September 2023 - ripe-atlas - mailman.ripe.net

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