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] AS number in traceroute data
- Previous message (by thread): [atlas] AS number in traceroute data
- Next message (by thread): [atlas] AS number in traceroute data
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Peter Gervai
grinapo+ripeatlas at gmail.com
Mon Apr 29 17:09:17 CEST 2013
On Mon, Apr 29, 2013 at 3:01 PM, Rumen Svobodnikov <rumen at telecoms.bg> wrote: >> No, there's no support for this on the probes. It'd be pretty expensive >> for >> to do this on the fly, as it involves a lookup (into BGP or IRRs) for >> virtually every packet received. > Doesn't sound so hard to implement, could be done via a DNS lookup. > For instance if you want to check what is the AS for IP 1.2.3.4, you do a > DNS lookup for 4.3.2.1.whatismyas.example.com and get the result. > This will move the complexity away from the tiny probe and to a place where > some complexity wouldn't be a problem (i.e. a DNS server). Or as a real-world example: dig TXT 4.3.2.1.asn.routeviews.org or dig TXT 4.3.2.1.origin.asn.cymru.com or dig TXT 4.3.2.1.all.ascc.dnsbl.bit.nl cya, grin
- Previous message (by thread): [atlas] AS number in traceroute data
- Next message (by thread): [atlas] AS number in traceroute data
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]