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] tracing from anchor nodes
- Previous message (by thread): [atlas] tracing from anchor nodes
- Next message (by thread): [atlas] tracing from anchor nodes
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Klaus Darilion
klaus.mailinglists at pernau.at
Wed Jul 2 13:52:12 CEST 2014
On 02.07.2014 10:24, Gilles Massen wrote: > Hi, > > On 07/02/2014 10:19 AM, Klaus Darilion wrote: > >> According to DNSMON [1] r.ns.at IPv4 is not reachable from >> us-bos-as11488. Are there any tools available to analyse the problem >> from the anchor? E.g. performing a traceroute from the respective anchor >> node? > > Define an UDM, and set the anchor as source. Seems obvious, so maybe > I've misunderstood the problem? Ups, I have not known that anchors have a probe id and can be used like any other probe. Thanks Klaus PS: Meanwhile I found out the problem is a routing problem on the reverse path ....
- Previous message (by thread): [atlas] tracing from anchor nodes
- Next message (by thread): [atlas] tracing from anchor nodes
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]