ris-users

Download

ris-users@ripe.net

November 2015

3 participants
2 discussions

Issues with ASPATH from rib
by Pavel Odintsov 29 Nov '15

29 Nov '15

Hello! I'm trying to build mapping from IP to AS number with bgpdump-1.4.99.15 and my custom toolkit. So I downloaded dump http://archive.routeviews.org/bgpdata/2015.11/RIBS/rib.20151128.0600.bz2 and trying to parse it with bgpdump. For about 90% of full BGP table I'm getting correct values for ASPATH. For example for my ASN 198068 I got: TIME: 11/28/15 06:00:03 TYPE: TABLE_DUMP_V2/IPV4_UNICAST PREFIX: 46.36.223.0/24 SEQUENCE: 55029 FROM: 147.28.7.2 AS3130 ORIGINATED: 11/11/15 18:25:25 ORIGIN: IGP ASPATH: 3130 2914 9002 198068 NEXT_HOP: 147.28.7.2 MULTI_EXIT_DISC: 2 COMMUNITY: 2914:410 2914:1201 2914:2202 2914:3200 3130:380 But some prefixes I'm getting very strange ASPATH with ASN enclosed in curly quotes. For example you could look at: TIME: 11/28/15 06:00:01 TYPE: TABLE_DUMP_V2/IPV4_UNICAST PREFIX: 5.39.176.0/21 SEQUENCE: 5583 FROM: 147.28.7.1 AS3130 ORIGINATED: 11/13/15 08:02:15 ORIGIN: IGP ASPATH: 3130 2914 3356 8530 {198753} NEXT_HOP: 147.28.7.1 AGGREGATOR: AS8530 91.143.64.24 COMMUNITY: 2914:420 2914:1007 2914:2000 2914:3000 3130:380 How I should interpret this record "3130 2914 3356 8530 {198753}"? Who are origin for this prefix 8530 or 198753? After some time of digging to this data I got more strange example: TIME: 11/28/15 06:00:06 TYPE: TABLE_DUMP_V2/IPV4_UNICAST PREFIX: 69.43.64.0/18 SEQUENCE: 108538 FROM: 195.208.112.161 AS3277 ORIGINATED: 11/27/15 13:37:08 ORIGIN: IGP ASPATH: 3277 3267 174 32432 {6939,46887} NEXT_HOP: 195.208.112.161 AGGREGATOR: AS32432 38.88.209.254 COMMUNITY: 3277:3267 3277:65321 3277:65323 3277:65331 So I really haven't any ideas about this ASPATH: 3277 3267 174 32432 {6939,46887}. Could you clarify both cases (with single and multiple AS numbers) with curly quotes? -- Sincerely yours, Pavel Odintsov

2 1

New RIS Remote Route Collectors at CATNIX Barcelona, SwissIX Zurich, France-IX Paris and Marseille
by Colin Petrie 12 Nov '15

12 Nov '15

Dear colleagues, The RIPE NCC is pleased to announce three new Remote Route Collectors (RRCs) for the Routing Information Service (RIS). RRC18 is now online at CATNIX in Barcelona. We would like to thank Maria Isabel Gandia, Manel Pérez, and CSUC for their help. RRC20 is now online at SwissIX in Zurich. We would like to thank Ulf Kieber and SwissIX for their help. RRC21 is now online at France-IX Paris and France-IX Marseille, hosted in Paris. We would like to thank Arnaud Fenioux and FranceIX for their help. The data from these new collectors is already available via RIPEstat. The raw data will be available in the archives in the near future. Peering with RIS ---------------- If you would like to peer with us, please fill in the form at: http://www.ris.ripe.net/cgi-bin/peerreg.cgi For more information about peering with RIS, please see: https://www.ripe.net/analyse/internet-measurements/routing-information-serv… About RIS ------------- RIS aims to collect and store Border Gateway Protocol (BGP) routing information and make it publicly available for the Internet community. The RIPEstat tools that provide access to this data can help network operators troubleshoot routing problems by providing eBGP data collected over time without being limited to a single BGP view. RIS deploys RRCs at major Internet exchanges, where they peer with other networks. At this time, RIS has more than 600 peers at 18 different Internet exchanges. For more information, please see: https://ripe.net/ris/ If you have any further questions, please contact <ris at ripe.net> Regards, Colin Petrie Systems Engineer RIPE NCC

1 0