[33741] in North American Network Operators' Group
Re: Wierd Route (fwd)
daemon@ATHENA.MIT.EDU (Richard A. Steenbergen)
Mon Jan 22 15:21:12 2001
Date: Mon, 22 Jan 2001 15:18:19 -0500 (EST)
From: "Richard A. Steenbergen" <ras@e-gerbil.net>
To: Jon Stanley <nanog@rmrf.net>
Cc: sam reddy <reddys@qwestip.net>, nanog@merit.edu
Message-ID: <Pine.BSF.4.21.0101221453040.38591-100000@overlord.e-gerbil.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Errors-To: owner-nanog-outgoing@merit.edu
On Mon, Jan 22, 2001 at 12:12:47PM -0600, Jon Stanley wrote:
>
> I still fail to understand. If I am correct, AS3908 and AS209 are
> somehow related in that Qwest was required to sell off all long haul
> circuits that go into the former USWest territory. I wasn't aware
> that this impacted the Qwest IP backbone as well, however this has
> been brought to my attention. What I don't understand is why AS3908
> can't aggregate before advertising to C&W, which then goes into AS209.
c&w only? As seen from route-server.eodus.net:
Network Next Hop Metric LocPrf Weight Path
*>i63.145.64.84/30 209.1.40.52 1000 0 2548 1 3908 i
*>i63.145.64.212/30 209.1.40.52 1000 0 2548 1 3908 i
*>i63.145.65.32/30 209.1.40.52 1000 0 2548 1 3908 i
*>i63.145.65.76/30 209.1.40.52 1000 0 2548 1 3908 i
...
*>i64.47.0.117/32 209.1.40.51 1000 0 1 3908 14995 ?
*>i64.47.0.164/32 209.1.40.51 1000 0 1 3908 14995 ?
etc etc etc
64.47.0.117 = l0.mcr1.n1.lax4.broadbandoffice.net
64.47.0.164 = l0.mcr2.dcae.broadbandoffice.net
loopbacks? If for whatever reason qwest feels the need to leak their /30's
and /32's to bbn, it could at least be no-export.
--
Richard A Steenbergen <ras@e-gerbil.net> http://www.e-gerbil.net/ras
PGP Key ID: 0x138EA177 (67 29 D7 BC E8 18 3E DA B2 46 B3 D8 14 36 FE B6)
