[j-nsp] How to prefer short prefixes ?

[Doug Marschke]

The routing table always prefers the longest match.
You could play around with putting the routes into a different table and
create forwarding filters based off that table.



-----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 9:33 AM
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