AS number in traceroute data
Hello, Is it possible to perform RIPE Atlas measurements with a key "-A" that shows the number of autonomous systems? - Kind Regards, Pavel Veselovskiy, Samara State Aerospace University
On 2013.04.26. 12:14, Pavel Veselovskiy wrote:
Hello,
Is it possible to perform RIPE Atlas measurements with a key "-A" that shows the number of autonomous systems?
- Kind Regards, Pavel Veselovskiy, Samara State Aerospace University
Hello, 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. But it would be possible to annotate the results in some way, when storing them or when you access them. Is this something that would be interesting for others too? Regards, Robert PS: of course the task itself is far from trivial. Trying it out on a random Linux box gave me the "wrong AS" for almost half of the cases. I'm sure there could be extensive discussion around how to Do This Right in the first place :)
On Mon, 29 Apr 2013, Robert Kisteleki wrote:
On 2013.04.26. 12:14, Pavel Veselovskiy wrote:
Hello,
Is it possible to perform RIPE Atlas measurements with a key "-A" that shows the number of autonomous systems?
- Kind Regards, Pavel Veselovskiy, Samara State Aerospace University
Hello,
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.
But it would be possible to annotate the results in some way, when storing them or when you access them. Is this something that would be interesting for others too?
Regards, Robert
PS: of course the task itself is far from trivial. Trying it out on a random Linux box gave me the "wrong AS" for almost half of the cases. I'm sure there could be extensive discussion around how to Do This Right in the first place :)
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).
On Mon, Apr 29, 2013 at 3:01 PM, Rumen Svobodnikov <rumen@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
Hi On 04/29, Robert Kisteleki wrote:
On 2013.04.26. 12:14, Pavel Veselovskiy wrote:
Is it possible to perform RIPE Atlas measurements with a key "-A" that shows the number of autonomous systems?
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.
But it would be possible to annotate the results in some way, when storing them or when you access them. Is this something that would be interesting for others too?
Annotations would make sense and it would be interesting to me. Otoh, this is also something that can be easily implemented on a case-by-case basis by atlas users in their own scripts when parsing the RIPE atlas probe results. gr, Lex -- LRO-RIPE | 570DE0BE | 9BF5 922E AF87 8584 E9CA C3AD C508 39A9 570D E0BE
On Mon, Apr 29, 2013 at 5:01 PM, Lex van Roon <r3boot@r3blog.nl> wrote:
Hi
Hi,
On 04/29, Robert Kisteleki wrote:
On 2013.04.26. 12:14, Pavel Veselovskiy wrote:
Is it possible to perform RIPE Atlas measurements with a key "-A" that shows the number of autonomous systems?
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.
But it would be possible to annotate the results in some way, when storing them or when you access them. Is this something that would be interesting for others too?
Annotations would make sense and it would be interesting to me. Otoh, this is also something that can be easily implemented on a case-by-case basis by atlas users in their own scripts when parsing the RIPE atlas probe results.
I entirely agree. To me, the right place to implement this sort of smarts is on the client side's userland. The new github community repo is a good starting point in that direction. I, for one, would be comfortable using a client* that would perform all the transformations/operations locally after consuming vanilla data straight from the Atlas API. Regards, Iñigo Ortiz de Urbina Cazenave * Ideally, an extensible client, part of a bigger, collaborative framework :-)
gr, Lex -- LRO-RIPE | 570DE0BE | 9BF5 922E AF87 8584 E9CA C3AD C508 39A9 570D E0BE
participants (6)
-
Iñigo Ortiz de Urbina -
Lex van Roon -
Pavel Veselovskiy -
Peter Gervai -
Robert Kisteleki -
Rumen Svobodnikov