This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/ripe-atlas@ripe.net/
[atlas] RIPE Atlas V1 Probe Issue
- Previous message (by thread): [atlas] Introducing blitzortung.org Network for Lightning and Thunderstorms in Real Time
- Next message (by thread): [atlas] RIPE Atlas V1 Probe Issue
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Alun Davies
adavies at ripe.net
Tue May 16 16:22:01 CEST 2017
Hello all, Due to an unfortunate bug in a recently released probe firmware (version 4760), a number of RIPE Atlas V1 probes are not currently able to connect to the network. The bug leads to excessive memory fragmentation which impacts that V1 probes because they have no MMU and only 8 MByte worth of memory. For reasons that are not yet clear, the issue has only affected well below half of the V1 probes. We are working on a new firmware that will correct this issue, but probes that will not connect will need to be returned to the RIPE NCC in order for the fix to be carried out. Once the new firmware is ready, users can either return their V1 probes to us to be fixed, or request a V3 probe instead. Thank you to Wilfred Woeber for reporting this and requesting an update on the current issue with the V1 probes. Cheers, Alun Davies RIPE NCC -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 2607 bytes Desc: not available URL: </ripe/mail/archives/ripe-atlas/attachments/20170516/1e025164/attachment.p7s>
- Previous message (by thread): [atlas] Introducing blitzortung.org Network for Lightning and Thunderstorms in Real Time
- Next message (by thread): [atlas] RIPE Atlas V1 Probe Issue
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]