[j-nsp] How to prefer short prefixes ?

[Scott Morris]

I believe the whole world works with the idea of longest-prefix match.  Any
other features that you change are to prevent a TIE in routes of the same
prefix length (like local pref, origin, AS-Path, etc.)...

So I think you may do what we all do.  Filter things.  Perhaps just a
generic filter there for only accepting /19's or bigger.  Or as specific as
you want for this particular case.

Or you can ask the announcer to stop doing that, but most likely won't
happen.  

Do make sure to ask WHY something is being advertised that way!  Perhaps
there is some relationship that makes it necessary.  While you/your company
may not care, others might.

Just a thought.  But can't change the routing world that easily other than
filtering.

HTH,

Scott
swm at emanon.com
 

-----Original Message-----
From: juniper-nsp-bounces at puck.nether.net
[mailto:juniper-nsp-bounces at puck.nether.net] On Behalf Of Tommy J
Sent: Thursday, September 28, 2006 12:33 PM
To: juniper-nsp at puck.nether.net
Subject: [j-nsp] How to prefer short prefixes ?

Hello 

I have a unique situation. 
We have a public peer who is announcing certain routes which of length /19
or shorter.  However we are also learning more specific routes (21-24) for
the same entity via our upstream (transit provider). Needless to say the
traffic bound for that entity uses our upstream. 

Is there is a way that where I can make the routes leaned via our public
peer more attractive ? Tweaking local pref does not work in this case
because the forwarding table always prefer more specific routes. 

TJ


__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around
http://mail.yahoo.com _______________________________________________
juniper-nsp mailing list juniper-nsp at puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp