[148552] in North American Network Operators' Group
Re: ANNOUNCE: bgptables.merit.edu - understanding visibility of your
daemon@ATHENA.MIT.EDU (Arturo Servin)
Wed Jan 18 09:23:43 2012
From: Arturo Servin <arturo.servin@gmail.com>
In-Reply-To: <9E11240C-22DA-4B1D-8806-579F398B5284@merit.edu>
Date: Wed, 18 Jan 2012 12:22:46 -0200
To: Manish Karir <mkarir@merit.edu>
Cc: "nanog@nanog.org list" <nanog@nanog.org>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
For example for any given prefix to get which ASNs have =
originated that prefix over time and when.
I think that could be interesting for discovering if a prefix =
has been hijacked in the past.
RIS from RIPE NCC provides something like this:
http://www.ripe.net/data-tools/stats/ris/routing-information-service
We have used it to verify some "suspicious" announcements of =
prefixes.=20
Regards,
as
On 17 Jan 2012, at 19:52, Manish Karir wrote:
>=20
> Hi Arturo,
>=20
> We could easily archive older copies of the database when we update =
the data, but I think our issue right now
> is that we dont fully understand how to add the notion of time to the =
user interface and we dont understand how
> folks might want to use it. Do you have a simple use case description =
of an example which might help us
> figure out how the notion of time can help answer a question.? What =
would be an example of a query=20
> that uses time?
>=20
> Thanks.
> -manish
>=20
>=20
> On Jan 16, 2012, at 12:53 PM, Arturo Servin wrote:
>=20
>> Manish,
>>=20
>> Nice tool.
>>=20
>> Is it possible to see the "history" of a prefix?
>>=20
>>=20
>> Regards,
>> .as
>>=20
>> =09
>> =09
>> On 13 Jan 2012, at 18:19, Manish Karir wrote:
>>=20
>>>=20
>>> All,
>>>=20
>>> We would like to announce the availability of the bgpTables Project =
at Merit at: http://bgptables.merit.edu
>>> bgpTables allows users to easily navigate global routing table data =
collected via routviews.org. bgptables
>>> essentially processes the data collected at routeviews and makes is =
available in a somewhat easier
>>> to use interface. The goal of bgpTables is to represent global =
prefix and AS visibility information from the
>>> vantage point of the various bgp table views as seen at routeviews.=20=
>>> The data is currently updated nightly (EST) but we hope to improve =
this over time.=20
>>> Please see the FAQ (http://bgptables.merit.edu/faq.php) for some =
simple examples of how you can use bgpTables.
>>>=20
>>> Some examples:
>>> - You can query for a specific ASN by entering the text 'as' =
followed by the AS number into the search box. For example to query for =
information about AS 237 you would enter 'as237' [without quotation =
marks] into the search box and then click 'search'. You can then use the =
view navigator map to switch to different routing table views for this =
ASN
>>>=20
>>> - You can query for a specific prefix by directly entering the =
prefix into the search box. For example to query for information about =
prefix 12.0.0.0/8 you would simply enter '12.0.0.0/8' [without quotation =
marks] into the search box and then click 'search'. You can then use the =
view navigator map to switch to different routing table views for the =
prefix.
>>>=20
>>> - You can find a particular prefix that you might be interested in =
by running a 'contained within' query via the search box. For example to =
quickly browse a list of prefixes contained within 1.0.0.0/8 to find the =
particular prefix you might be interested in, you can enter the text =
'cw1.0.0.0/8' [without quotation marks] into the search box and click =
'search'. You can then browse the resulting table to select the =
particular prefix you might be interested in.
>>>=20
>>> - You can simply enter the text 'as' followed by the company name =
into the search box then click search to view a list of possible matches =
for that text. For example, to view all matching google ASNs you can =
simply enter 'asgoogle' into the search box and click search. A list of =
possible matching ASNs that reference Google by name will be returned =
from which you an then select the particular ASN that is of interest to =
you.
>>>=20
>>>=20
>>> Comments, corrections, and suggestions are very welcome. Please =
send them to mkarir@merit.edu. Hopefully folks will find this useful.
>>>=20
>>> Thanks.
>>> -The Merit Network Research and Development Team
>>>=20
>>=20
>=20
