On Mon, Nov 30, 2009 at 02:44:08PM +0200, Jussi Peltola wrote:
> This works for me:
> # NB: if a carp address is the lowest IP you will get duplicate
> # router-id's - maybe ospfd should ignore CARP interfaces when selecting
> # the host id?
>
> router-id 1.2.3.4
>
> area 0.0.0.0 {
> interface gif0 { } # link to another site
> interface gif1 { } # link to another site
> # ...
> interface vr1 { } # link to CARP peer
> interface carp1 { passive }
> interface carp2 { passive }
> interface carp3 { passive }
> }
>
> OSPF doesn't work over CARP interfaces. You need to connect to the rest
> of the OSPF cloud over "real" interfaces, and the CARP-connected
> networks should be stub networks where your actual hosts live. And CARP
> interfaces must be passive.
>
Sorry, I am still confused here. What I have is a pair of machines, each
machine has 3 physical interfaces. On each machine one is for the "inside"
network, one is for the "outside" network, and one is for phsync. The
inside network is a single subnet, and does not need to see OSPF routing,
as all of it's machines have a static default route to the CARP'd "inside"
interface. Both the "inside" and "outside" interfaces on both machines have
an equiv. CARP interface. So, there are 3 outside IP addresses. the CARP
address, and an individual address for the outside interface on each
machine.
In a perfect world, the advertised OSPF route would be the CARP'd IP
address. What can't happen is to have the machines both advertise their
real physical interface addresses as duplicate routes to the inside
network, right? And what happens at failover, if the advertised route is
not that of the CARP interface?
What am I misunderstanding here?
--
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?
