leakage of specifics of 204.70.0.0/16

i am still trying to understand why this is causing so much of a problem,
possibly masking a second bug. but i would appreciate knowing how
widespread the leakage is.

rg-tig0#sh ip bg 204.70.0.0 255.255.0.0 l

We're only picking up the ones tagged with MCI's internal AS's:

  *> 204.70.0.0/15 198.32.136.12 150 3561 i
  *> 204.70.128.0/21 198.32.136.12 150 3561 4292 i
  *> 204.70.138.0 198.32.136.12 150 3561 4281 i
  *> 204.70.139.0 198.32.136.12 150 3561 4286 ?
  *> 204.70.140.0 198.32.136.12 150 3561 4286 ?
  *> 204.70.141.0 198.32.136.12 150 3561 4286 ?
  *> 204.70.142.0 198.32.136.12 150 3561 4286 ?
  *> 204.70.144.0 198.32.136.12 150 3561 4286 i
  *> 204.70.145.0 198.32.136.12 150 3561 4286 ?
  *> 204.70.240.0/20 198.32.136.12 150 3561 4292 i

Notice we're picking up the /15 adv. I'm sure you can see it with a
255.254.0.0 query mask.

I see your stuff:

*> 204.71.144.0/21 198.32.136.12 150 3561 3927 i
*> 204.71.152.0 198.32.136.12 150 3561 3927 i
*> 204.71.153.0 198.32.136.12 150 3561 3927 i
*> 204.71.155.0 198.32.136.12 150 3561 3927 i
*> 204.71.156.0/22 198.32.136.12 150 3561 3927 i

You have 204.71.144.0/20. No aggregation? :wink:

Sounds like a route-map doesn't have a no-adv tag set right at MCI. You're
seeing all their IBGP stuff.

For me, it seems like kind of a waste to adv a bunch of specifics if they're
internal anyway :slight_smile: The ones above all use MCI's internal AS's. I'd just
like to see the /15, nothing else.

  rob.

   Network Next Hop Metric LocPrf Weight Path
*> 204.70.0.0/16 204.70.52.25 1000 0 3561 i
* 199.2.96.5 1000 0 3130 3561 i

[etc]