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] Reasons to celebrate - passed 1K active probes :)
- Previous message (by thread): [atlas] Reasons to celebrate - passed 1K active probes :)
- Next message (by thread): [atlas] Reasons to celebrate - passed 1K active probes :)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Philip Homburg
philip.homburg at ripe.net
Fri Dec 23 12:35:00 CET 2011
On 12/23/11 12:23 , Stephane Bortzmeyer wrote: > On Fri, Dec 23, 2011 at 12:12:51PM +0100, > Philip Homburg<philip.homburg at ripe.net> wrote > a message of 16 lines which said: > >> releasing the source code [...] allow probes with unknown firmware >> connect to the atlas infrastructure. > That's two completely different things. I mentioned only the first > one. In my vision, modified probes were intended for another C&C, not > for the Atlas service. > Okay. I assumed that with 'with instructions on how to build your own probe' you meant how to connect it to the Atlas infrastructure. But if you want to connect the probe to another C&C then you may also need the source code for the back-end. The software that runs on the probe is quite simple. The back-end is a completely different story.
- Previous message (by thread): [atlas] Reasons to celebrate - passed 1K active probes :)
- Next message (by thread): [atlas] Reasons to celebrate - passed 1K active probes :)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]