[quagga-users 13004] Re: Static route to IP learned from OSPF
quagga-users at alexis.users.panix.com
Mon Oct 22 14:15:22 BST 2012
On Oct 22, 2012, at 6:51 AM, Bret Clark wrote:
> No R1 has to have a default to R2 and R2 has to have a default to R3...you're better off adding the following under R3's OSPF routing configuration:
> "default-information originate always"
> The default route will be passed to R1 and R2 via OSPF.
That's not correct. There is no reason you can't have a static pointing to a learned route. There is no need for a "helper" route (such as a default from R2) as the /32 is learned in OSPF. The static should be installed in the route table when the learned route appears, and be removed when it is lost.
You might run into a problem because of a Quagga bug, however. I'm not sure I recall the specifics, but I think that it fails to delete static routes from the route table when the learned (OSPF) route it depends on goes away. Someone else on this list can probably point you to the bug. I believe there are at least two proposed patches previously posted to this list to fix this problem (and you need look no further than there to see that the call for additional maintainers is justified - this has been the case for years now).
> On 10/22/2012 05:49 AM, Mattias Walström wrote:
>> I wondering if the following topology should work, we got a request to do following:
>> R1 <=======> R2 <==========> R3
>> 10.0.0.0/24 10.1.0.0/24 10.10.10.10/32
>> all routes are distributed in OSPF with redistribute connected, R1 will now know about 10.10.10.10 through R2.
>> now adding following in zebra on R1:
>> ip route 0.0.0.0/0 10.10.10.10
>> Is this really a valid configuration, to have a static route to an IP only learned from OSPF?
More information about the Quagga-users