Ernst, just update SSH keys in probe’s General tab (the last Edit item on the page) so probe will preserve its number. Regards, Grzegorz From: "Ernst J. Oud" <ernstoud@gmail.com> Date: Monday 2022-06-20 at 19:09 To: "ripe-atlas@ripe.net" <ripe-atlas@ripe.net> Subject: Re: [atlas] No data for ping to second hop? 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<https://urldefense.com/v3/__https:/github.com/moby/vpnkit/pull/302__;!!GjvTz_vk!S--9Zq7Z1la9xPmFuT5ThfyRwGyM_9xY5NG-GOjxnyuc6cmWSJMHd47kqDo0UoAs8-teyZqRxo_L0gs$> (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@ripe.net wrote: Re: No data for ping to second hop?