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 ]
ripe at brite.cz
ripe at brite.cz
Sun Jun 19 14:37:39 CEST 2022
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 at gmail.com> > Komu: ripe-atlas at 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 at ripe.net >https://mailman.ripe.net/ > >
- 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 ]