BBN issues

Danny McPherson danny at
Tue Dec 14 00:14:50 UTC 1999

> You don't see the NY -> Cali -> NY path? That is a bad thing (tm).

In the first traceroute it did initially seem interesting, although my 
presumption was that Sprint likely wasn't leaking routes (or providing 
transit?) "everywhere", and probably only via that specific path, as 
demonstrated.  Another observation to that regard is that the [leaked?] prefix 
was presumably a more specific, else [theoretically], Genuity would have 
selected the shorter AS path .. although BBN/GTEI may perhaps be providing 
that transit via there AS, which would even things out from a path vector 

(The reverse path seems somewhat reasonable considering BBN and Genuity are 
still separate ASs with distinct network and interconnection topologies.

I do still see potential brokenness wrt route leakage and the like, so either Sprint is still leaking routes or GTEI is attempting to offload (via a psuedo transit connection) some of that Genuity hosting traffic elsewhere...  

Of course, I'd really suggest now that we avoid dicussing this specifically on the list and leave the problem resolution to the folks that can actually fix it/them, if they actually exist.


More information about the NANOG mailing list