|
North American Network Operators Group Date Prev | Date Next | Date Index | Thread Index | Author Index | Historical IRR route entries
At http://compute.merit.edu/problems.html, there is a list of routes being advertised with ASs inconsistent with those in the IRR. I'm having a bit of trouble understading a few things. I will take an example of 192.139.72.0/24, which is one of our client's blocks. It shows up with an inconsistent origin AS in http://compute.merit.edu/stats/mae-east/problems/IRR/3561.960930.html: 192.139.72.0/24 192.41.177.181 (3561 577 852 6171 IGP) [ AS2493 AS2493] 6171 is the AS that it should be originating from, however according to this it appears that at least something thinks it should be coming from AS2493, who used to be our provider until perhaps six or eight months ago when we dropped them because they were simply too clueless to make things work. Our new provider is AS852; our advertisements were coming from them for a while until CA*net figured out how make things work with us talking BGP to AS852 who talks BGP to CA*net (AS577, at least for their backbone). You may remember me asking about advisory attributes a few weeks back; that was because CA*net was trying to tell us that the reason our route advertisements weren't making it past CA*net's borders was because our entries didn't have an advisory field in them. Thanks for the responses on that one; I thought the advisory attribute was obsolete, but CA*net insisted it was needed. Interestingly enough, the other change we told them to make in the routing database which they said wouldn't do anything was made and when it was made things did start working. <sigh> Anyway, back to the issue at hand: All our IRR updates are done into the CA*net routing database (crcd). current situation appears to be as follows: Script started on Tue Oct 1 09:24:40 1996 [email protected]:/usr/var/tmp$ whois -h whois.canet.ca 192.139.72.0 route: 192.139.72.0/24 descr: NET-LI01 origin: AS6171 remarks: AGT Advanced Communications - WorldGate mnt-by: CANET-RC changed: [email protected] 960612 source: CANET route: 192.139.0.0/16 descr: NETBLK-CANET-192-139 origin: AS577 comm-list: CANET_PROXY_AGGRS mnt-by: CANET-RC changed: [email protected] 950419 source: CANET route: 192.139.72.0/24 descr: NET-LI01 origin: AS2493 mnt-by: CANET-RC changed: [email protected] 960503 source: CANIX [From this, it appears to me like the first one should be preferred because of the date on it.] [email protected]:/usr/var/tmp$ whois -h whois.ra.net 192.139.72.0 route: 192.139.72.0/24 descr: NET-LI01 origin: AS6171 advisory: AS690 1:3561(11) 2:3561(144) 3:3561(27) 4:3561(218) 5:3561(147) remarks: AGT Advanced Communications - WorldGate mnt-by: CANET-RC changed: [email protected] 960612 source: CANET route: 192.139.72.0/24 descr: NET-LI01 origin: AS852 advisory: AS690 1:3561(11) 2:3561(144) 3:3561(27) 4:3561(218) 5:3561(147) remarks: AGT Advanced Communications - WorldGate mnt-by: CANET-RC changed: [email protected] 960612 source: CANET [AFAIK, the above one was deleted from the crcd on 960612, at the same time the one above it was added.] route: 192.139.72.0/24 descr: NET-LI01 origin: AS542 advisory: AS690 1:3561(11) 2:3561(144) 3:3561(27) 4:3561(218) 5:3561(147) mnt-by: CANET-RC changed: [email protected] 960207 source: CANET [This one is left over from our old provider before I*Star bought them.] route: 192.139.72.0/24 descr: NET-LI01 origin: AS2493 mnt-by: MAINT-AS2493 changed: [email protected] 960503 source: ANS route: 192.139.72.0/24 descr: NET-LI01 origin: AS2493 mnt-by: MAINT-AS2493 changed: [email protected] 960503 source: MCI [The above two are from our old provider after they were bought by IStar, aka AS2493. Does the source mean that they are submitting them directly to ANS and MCI? My best guess on the situation is that, for some reason, AS2493 is submitting updates to MCI and ANS, who are their service providers, and they are being preferred over the correct ones.] [email protected]:/usr/var/tmp$ whois -h whois.ans.net 192.139.72.0 route: 192.139.72.0/24 descr: NET-LI01 origin: AS2493 mnt-by: MAINT-AS2493 changed: [email protected] 960503 source: ANS [ANS sure thinks AS2493 is the right one.] [email protected]:/usr/var/tmp$ Script done on Tue Oct 1 09:25:15 1996 There are also a few different problems with some of our other addresses, for example (from http://compute.merit.edu/stats/aads/problems/IRR/3561.960929.html): 207.167.0.0/19 198.32.130.12 (3561 577 852 6171 IGP) [] There should be no old providers screwing anything up here, since this is a newish block. It shows up in the CA*net database, at whois.ra.net, but is still listed as not being properly registered. There are others that are showing up, but these seem to be the two types of problems that are showing up. Can anyone provide any helpful hints on what is going on? Thanks. - - - - - - - - - - - - - - - - -
|