Hi Robert, weirdly, some of the SW probes are showing as "online" but do not provide any measurements results [event the Built-in ones], such as your mentioned 1000030 [Latest data point shown is from 2019-12-17 11:57 UTC] Also for example measurement https://atlas.ripe.net/measurements/23955368/ shows 18 out of 71 SW probes were online [at the moment when I created the measurement] but never provided any results. In https://atlas.ripe.net/measurements/23962519/ I requested all probes with tag system-software, you can see how many probes are Online while not providing any results.
What I wanted to point out - I run SW probe 1000069 in Turris Omnia router and I noticed the same behavior - after router restart the SW probe goes online and looks fine, but does not send any results, until I restart the ATLAS process manually, then it runs fine until next router's reboot / power cycle. Cheers Jiri ______________________________________________________________ > Od: "Robert Kisteleki" <rob...@ripe.net> > Komu: "Romain Fontugne" <rom...@iij.ad.jp> > Datum: 14.02.2020 10:38 > Předmět: Re: [atlas] [mat-wg] RIPE Atlas Software Probes > > CC: <email@example.com> > >To be fair the v1 and v2 (ID<=5000) are 9+ years old tiny embedded >devices, their capabilities are nowhere close to anything else one runs >Linux on nowadays. > >Note that our team is also analysing the similarities/differences, but >if someone else also wants to look, these are good candidates (same AS, >same prefix, approximately same location): > >https://atlas.ripe.net/probes/1000030/ (sw) >https://atlas.ripe.net/probes/28270/ (v3) > >or: > >https://atlas.ripe.net/probes/1000041/ (sw) >https://atlas.ripe.net/probes/54558/ (v4) > >Cheers, >Robert > > >On 2020-02-14 02:42, Romain Fontugne wrote: >> my non-scientific comparison: looking at RTTs in traceroutes the old v1 >> seems a msec slower. All are very stable >> >> Romain >> >> >> On 2/14/20 4:12 AM, Randy Bush wrote: >>> if someone wants to compare, 4981 (a lovable old v1), 1000004, and >>> 1000006 are on the same lan segment in the same pop with the same vrrp >>> exit etc. >>> >>> randy >>> >> > > >