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] v3 probe has gone offline and can't be revived
- Previous message (by thread): [atlas] v3 probe has gone offline and can't be revived
- Next message (by thread): [atlas] Announcement regarding the recently discovered log4j vulnerabilities
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Peter Gutmann
pgut001 at cs.auckland.ac.nz
Tue Dec 21 14:30:22 CET 2021
I wrote: >Does anyone have any ideas on where to go from here? So the answer was "reboot the managed switch it's connected to, which seems to be too smart for its own good". Moving it to a different port made no difference but rebooting brought it back on the original port. Peter.
- Previous message (by thread): [atlas] v3 probe has gone offline and can't be revived
- Next message (by thread): [atlas] Announcement regarding the recently discovered log4j vulnerabilities
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]