It actually means the second hop router simply does not reply ping. It is common with ISP routers. Usually the first hop is youre own home router, the second is Provider's end. When you riun tracert you may see like this: traceroute to www.turris.cz (217.31.192.69), 30 hops max, 38 byte packets 1 10.11.5.146 0.724 ms 2 * 3 78.110.208.41 4.866 ms 4 78.110.222.105 5.656 ms 5 91.213.211.132 4.993 ms ... Thats exactly the symptom you see ______________________________________________________________
Od: "Ernst J. Oud" <ernstoud@gmail.com> Komu: ripe-atlas@ripe.net Datum: 18.06.2022 15:16 Předmět: [atlas] No data for ping to second hop?
Hi,
Out of curiosity, all my “Built-ins” in my software probe show data except ”#2 Second Hop to ping.ripe.net (193.0.0.164)” which shows:
“No data available for [Probe ID] / 2 for this time period.”
Any advice?
Regards,
Ernst
Update: This appears to be a docker for Windows issue. My software probe runs on Alpine Linux in docker on Windows 10 WSL. Investigating further…
----------
-- ripe-atlas mailing list ripe-atlas@ripe.net https://lists.ripe.net/mailman/listinfo/ripe-atlas