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/[email protected]/
[atlas] Any way to select the probes from upstream AS (not origin AS)?
- Previous message (by thread): [atlas] Any way to select the probes from upstream AS (not origin AS)?
- Next message (by thread): [atlas] Any way to select the probes from upstream AS (not origin AS)?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Stephane Bortzmeyer
bortzmeyer at nic.fr
Wed Nov 11 17:03:15 CET 2015
On Wed, Nov 11, 2015 at 04:43:49PM +0100, Robert Kisteleki <robert at ripe.net> wrote a message of 14 lines which said: > No, we don't have direct support for this. I guess one could > download latest traceroute results for a (random) built-in > measurement, map IPs to ASNs and use that -- but I have to admit > it's not easy. I understand. Also, a probe has one origin AS but may have several upstream AS and you don't know which one will be used when the probe fires a packet to the target.
- Previous message (by thread): [atlas] Any way to select the probes from upstream AS (not origin AS)?
- Next message (by thread): [atlas] Any way to select the probes from upstream AS (not origin AS)?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]