On 2008/01/17 16:21, Alexander Burnos wrote: > Hello! > > On Thu, Jan 17, 2008 at 02:07:01PM +0000, Stuart Henderson wrote: > > > I want to setup fallback to a static default route if bgp fails. > > > I receive default route via bgp but I want to use static automatically > > > if bgp session is down of default prefix isn't received. > > > Is it possible? How can I do that? > > > > I think the only way you can do something similar to what you're > > asking for is by filtering the BGP default, and adding your own > > static default (typical BSD routing tables don't support multiple > > routes to the same destination, we do support it for equal-cost > > multipath but not for different priority routes which I think is > > what you want). > > It isn't my way because actually I have two 'default route' sources: eBGP > and iBGP. If eBGP 'default route' fails I'll use iBGP information. > I can't override them with one static route because I'll lose > redundancy if main uplink fails.
Ah, so you don't receive a full table by ibgp when your ebgp peer is down? (if you do, there's no problem, as the more-specifics would override the static default). > I decided to went another way and configure 'reply-to' feature of pf: It's my understanding (and a 5-second test seems to bear this out) that you still need a route in the routing-table matching the destination otherwise things won't get far enough up the stack to reach PF.
