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] No data for ping to second hop?
- Previous message (by thread): [atlas] No data for ping to second hop?
- Next message (by thread): [atlas] No data for ping to second hop?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Ernst J. Oud
ernstoud at gmail.com
Mon Jun 20 19:09:01 CEST 2022
Hi, Thanks for the reply. But it appears to be a common problem for Linux containers in Docker Desktop for Windows. All traceroute commands only show asterisks. As explained here: https://github.com/moby/vpnkit/pull/302 (vpnkit is used by Docker in Windows). So I will have to install the probe in a native Linux environment instead. Which raises another question: if I get the probe running in native Linux, can I transfer my current probe ID to this new installation? Or do I have to apply for a new probe (and disconnect the other)? Regards, Ernst > On 20 Jun 2022, at 12:00, ripe-atlas-request at ripe.net wrote: > > Re: No data for ping to second hop? -------------- next part -------------- An HTML attachment was scrubbed... URL: </ripe/mail/archives/ripe-atlas/attachments/20220620/cbf83a18/attachment.html>
- Previous message (by thread): [atlas] No data for ping to second hop?
- Next message (by thread): [atlas] No data for ping to second hop?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]