North American Network Operators Group
Date Prev | Date Next | Date Index | Thread Index | Author Index | Historical

Re: /24 multihoming issue

  • From: Kyaw Khine
  • Date: Thu Oct 20 02:40:19 2005
  • Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:Received:Date:From:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=PGOZaEdYtLz0nZPLmZr2SmCyuFxlbU9lbxW3q9rivmS2uZW83MT6Ypqq1bplXALvimuJBu+vSBGF+hNSrEVOVcSo9lozCm6Ad9OY0NJyO2sKEZ47uOrzVMvgGG/bEVEoYkqoGtS9uGfu+rIrGFoKNT9iQTFMtIF1w1KpO8pFROM= ;
I got an answer for my question.
7018/ATT does ACCEPT /24 routes from 701/mci.
e.g
24.143.13.0/24 on route-server.ip.att.net
has AS-PATH (7018 701 13368). 

Is 7018 preferring 19094 over 701 regardless of
AS-PATH length? Or, 7018 will not take prefixes from
other peers if a particular prefix is coming from
19094 regardless of AS-PATH?

** 7018 is just an example. There a quite a few ISP
with the same behavior.

Well .. I'm still in the maze.

--- Kyaw Khine <[email protected]> wrote:

> Says .. I pick 7018/AT&T.
> 7018 is accepting 701/mci customer routes. But is
> 7018
> accepting 701/mci customer /24 routes ???
> 7018 is definitely accepting 19094/telcove /24
> routes
> because I see 64.9.17.0/24 on ATT route-server
> (route-server.ip.att.net)
> 
> So, why is 7018 receiving/accepting /24 from some
> peers (19094) but not from others (701)???
> 
> That .. I can't figure out.
> 
> 
> 
> 	
> 		
> __________________________________ 
> Yahoo! Mail - PC Magazine Editors' Choice 2005 
> http://mail.yahoo.com
> 



		
__________________________________ 
Yahoo! Music Unlimited 
Access over 1 million songs. Try it free.
http://music.yahoo.com/unlimited/