I did the experiment, and it was successful: probe appeared 8 minutes
after booting with a new flash key. I'd say we need more statistics, but
sometimes it works.
--
With Best Regards,
Marat Khalili
On 19/05/16 17:47, Boris Fersing wrote:
Hi,
I was asking because I had a similar issue recen
>From both my own (short term) experience and from what's being written on this
>list, I'm getting the impression that the USB drive may be costing more than
>it's worth.
I have in only about 3 months experienced multiple probe issues due to USB
drives and there have been multiple threads on t
Dear colleagues,
Please find a new article on RIPE Labs demonstrating the value of the
results collected by RIPE Atlas independent of the original purpose for
collecting them. Using all traceroute results from a particular day as
an example, we first show that near real-time analysis of the result
On 20/05/2016 15:37, Michael Ionescu wrote:
Interesting idea to make the USB drive optional. Based on literature:
https://en.wikipedia.org/wiki/USB_flash_drive#Failures
https://askleo.com/can_a_usb_thumbdrive_wear_out/ - 10,000-100,000
http://cfgearblog.blogspot.co.il/2011/03/how-long-does-flash
Hi,
On Fri, May 20, 2016 at 02:37:44PM +0200, Michael Ionescu wrote:
> >From both my own (short term) experience and from what's being written on
> >this list, I'm getting the impression that the USB drive may be costing more
> >than it's worth.
[..]
> Any thoughts?
The USB outages and the lac
+1. I lost most of the probes this way and I'm not really sure how to
recover them - I need to ask for a batch of USB drives or ask all the hosts
to remove them... can't this be handled better with a firmware replacement?
I would at least then ask all the hosts to unplug the USB and leave the
hosts
On 2016/05/20 14:37 , Michael Ionescu wrote:
> If the main reason for the drive is to cache data during unavailability
> of the command and control center, this may not be worth the effort.
No, the probe actually runs from the USB stick. The internal 4MB flash
is just enough to initialize the USB
On 2016/05/20 14:57 , Hank Nussbacher wrote:
> Has anyone tested how many writes are going on to the ATLAS thumb
> drive? Perhaps with all the failures within a year of start, perhaps
> too many writes are taking place?
We have no clear idea why they fail. It seems that time to failure is
highly
Hi,
On Fri, May 20, 2016 at 04:10:47PM +0200, Philip Homburg wrote:
> We have no clear idea why they fail. It seems that time to failure is
> highly variable.
Can you correlate tests-until-failure or data-written-until-failure?
One of mine has failed at least two times now, and it could be that
So I have a few theories. I have now had 3 different USB sticks fail on me:
Two Sandisk 4GB SDCZ33 and one cheap generic 8GB replacement.
The power draw of the TP-Link system + USB is probably more than the
opportunistic USB ports they get plugged in to. An underpowered probe runs
great MOST of th
Hi,
How can it be that the status of a probe is down while I see current DNS
requests in the SOS list without any remarks in the 'info' column? Even
the power-up time is increasing.
If the probe can send DNS requests, why does it not have some mechanism
to recover? Seem not too hard to make
No. Everything seemed normal except that it was down. All tags like
"IPv4 works" etc. were there. The only thing was that the status was down.
So I pulled the power, pulled USB, replaced the power. Went to brush my
teeth and came back to replace USB and went to bed around 23:30 (21:30UTC)
A f
12 matches
Mail list logo
