Re: [atlas] probe coverage map?
Is this what you are looking for? https://atlas.ripe.net/results/maps/network-coverage/ On Wednesday, May 18, 2016, Bajpai, Vaibhav wrote: > Hello, > > What happened to the probe coverage map that showed number of probes > at different level of details depending on the zoomed-in state of > the map? — I have an earlier screenshot [a] (2015) to explain what > I mean. It was a very nice plot. > > [a] http://i.imgur.com/d0tI1qP.png > > I was looking for a probe coverage map to put in one of my slides. > I ended up using [b], but I miss [a]. > > [b] > https://www-static.ripe.net/static/rnd-ui/atlas/static/page/img/allprobes.png > > Best, Vaibhav > > === > Vaibhav Bajpai > www.vaibhavbajpai.com > > Room 91, Research I > School of Engineering and Sciences > Jacobs University Bremen, Germany > === >
Re: [atlas] Incorrect probe connection information?
I've noticed that well. My probe is displaying 100% uptime, even though it has been offline due to power outages. On Monday, April 11, 2016, Max Mühlbronner wrote: > Hi, > > > I think there is a small bug/issue with the statistics of the probe (Tab : > "Network") : > > Connection Information > > Time Connected Percent > Last Week 9d 10h 2m 100.00% > Last Month 55d 10h 2m 100.00% > > How could it be that Last Month my probe was connected for 55 days? (It's > only a single probe) > > Any idea? > > > Best Regards > > > Max M. >
Re: [atlas] An article/FAQ entry about probe troubleshooting
An issue with having a FAQ for the failing USBs is that people will perform the procedure when it is not necessary. I think though that there should still be more debugging info for connections. On Monday, January 25, 2016, wrote: > +1 ! > > Sarah > > - Mail original - > De: "Ondřej Caletka" > > À: ripe-atlas@ripe.net > Envoyé: Lundi 25 Janvier 2016 16:20:50 > Objet: [atlas] An article/FAQ entry about probe troubleshooting > > Hi all, > > it seems that failing probes are getting more and more to be an issue, > possibly due to USB flash drive failure. I think it would be nice if > there was an article / FAQ entry with some official troubleshooting > procedures, so we could just send a link to anybody complaining about > non functional probe. > > Is there something like this on the roadmap? Perhaps we as the community > could make something up: > > - how to check whether the port probe is connected to has proper IP and > DNS parameters and is allowed to establish a SSH session to TCP port 443 > in the Internet (beware of DPI firewalls that allow HTTPS but not SSH > over 443) > > - how to check the LED status and the SOS list at the probe page (the > current LED explanation in the FAQ is too techy and even power users > like me still don't understand all presented states :) ) > > - how to diagnose USB flash drive failure, how to force reformatting > the flash drive and how to replace it with a new one > > > What do you think? > > Cheers, > Ondřej Caletka > CESNET > > >
Re: [atlas] integrity checks for the Atlas software?
I think that is completely possible. The only issue is that it will take up far more resources validating the integrity of the code (which could be used for measurements). On Tuesday, 12 January 2016, Wilfried Woeber wrote: > > While thinking about options or mechanisms to make virtual probes > "tamper-proof" > I had this question coming up: > > Is the probe software capable to "verify" (check-sum or digital sig) the > bootstrap > kit and then, during run-time, verify that the code in memory is still > genuine? > > Thanks, > Wilfried > > >
