Hi, I noticed that of the probes I checked here in The Netherlands, all logging stops at around 03:00 today (June, 22nd). Checked a probe in Germany, same thing but stopped a couple of hours later it seems. Is there some problem? Regards, Ernst J. Oud
On 21 Jun 2022, at 12:00, ripe-atlas-request@ripe.net wrote:
Send ripe-atlas mailing list submissions to ripe-atlas@ripe.net
To subscribe or unsubscribe via the World Wide Web, visit https://lists.ripe.net/mailman/listinfo/ripe-atlas or, via email, send a message with subject or body 'help' to ripe-atlas-request@ripe.net
You can reach the person managing the list at ripe-atlas-owner@ripe.net
When replying, please edit your Subject line so it is more specific than "Re: Contents of ripe-atlas digest..."
Today's Topics:
1. Re: No data for ping to second hop? (Ernst J. Oud) 2. Re: No data for ping to second hop? (Ponikierski, Grzegorz)
----------------------------------------------------------------------
Message: 1 Date: Mon, 20 Jun 2022 19:09:01 +0200 From: "Ernst J. Oud" <ernstoud@gmail.com> To: ripe-atlas@ripe.net Subject: Re: [atlas] No data for ping to second hop? Message-ID: <E7C26305-00C5-4527-9FE1-F0534352F82E@gmail.com> Content-Type: text/plain; charset="us-ascii"
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@ripe.net wrote:
Re: No data for ping to second hop?