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] Fwd: Deleting/editing a UDM: Not Owner

Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Andreas Strikos astrikos at ripe.net
Wed Jul 2 10:29:13 CEST 2014

Hi Klaus,

DSNMON itself is doing also traceroutes. So, for each anchor you can see 
its traceroute towards each target.
You have to click on a specific tile and you will get a pop up window 
with the closest time-wise traceroute(s).

Regards,
Andreas

On 7/2/14, 10:19 AM, Klaus Darilion wrote:
> Hi!
>
> 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?
>
> Thanks
> Klaus
>
>
> [1]
> https://atlas.ripe.net/dnsmon/group/at.?dnsmon.session.color_range_pls=0-66-66-99-100&dnsmon.session.exclude-errors=true&dnsmon.type=server-probes&dnsmon.server=194.0.25.10&dnsmon.zone=at.&dnsmon.startTime=1404246000&dnsmon.endTime=1404288000&dnsmon.ipVersion=both
>

Previous message (by thread): [atlas] tracing from anchor nodes
Next message (by thread): [atlas] Fwd: Deleting/editing a UDM: Not Owner

Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

[ ripe-atlas Archives ]