Re: Strange static route

On Fri, Sep 23, 2011 at 8:57 PM, jim deleskie <deleskie@gmail.com> wrote:

Wouldn't it make more sense to filter in bound default?  or use a single static default if you where worried about that?

Yes, the aesthetics of using a "/1 route" for that purpose are very poor. Don't implement design objectives using subtle side-effects, when a proper tool is available -- human errors later are likely. Using a /1 static to achieve a "longer prefix" to override a default falls in that category, when routers have a filtering mechanism capable of explicitly expressing the desired policy :)

-jim -- -JH