On 2013/10/02 12:26, Andy wrote: > "No, but does it matter anyway?" - Good point.. What I should have > really asked is how can I ensure that the route with the lowest > metric/cost is the one pointing to the master..
ospfd does that anyway (and DR/BDR are only ospf roles determining who synchronizes with other routers, it doesn't affect which is preferred for routing) > ""Reinstate ospfd(8) code to announce routes to backup carp > interfaces, so that a specific route is maintained during failover." > ..which I think means it actually will announce it when being carp > slave, but with a higher cost/metric/whateveritsname." > > !! This would be amazing and exactly what I'm after :) (assuming that > the carp backup announces with a higher cost..) before this fix (which you could easily backport to 5.3 if needed) then only the carp master would announce the route so it still did pretty much what you need; this fix reinstates the code which makes both backup+master announce into ospf so the route doesn't dropout (reducing the chance of evil cloned default routes)
