On Tue, Dec 01, 2009 at 11:55:26PM +0200, Jussi Peltola wrote:
> This is normal. The Linkstate column shows the CARP state, and the
> interface is passive so it is DOWN - you do not run OSPF on it so there
> are no neighbors.
>
OK, thanks for clarifying the final point on this.
--
A: Because it
This is normal. The Linkstate column shows the CARP state, and the
interface is passive so it is DOWN - you do not run OSPF on it so there
are no neighbors.
On Mon, Nov 30, 2009 at 09:31:19PM +, Stuart Henderson wrote:
> On 2009-11-30, stan wrote:
> > 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,
On Mon, Nov 30, 2009 at 09:31:19PM +, Stuart Henderson wrote:
> On 2009-11-30, stan wrote:
> > 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,
On Mon, Nov 30, 2009 at 09:31:19PM +, Stuart Henderson wrote:
> On 2009-11-30, stan wrote:
> > 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,
On Tue, Dec 01, 2009 at 06:17:32AM -0500, stan wrote:
> On Mon, Nov 30, 2009 at 11:29:00PM +0200, Jussi Peltola wrote:
> > Not knowing your network I can only guess you don't want to mix CARP and
> > OSPF on the "outside" interfaces. OSPF will handle the fail-over.
> >
> > CARP interfaces listed i
On Mon, Nov 30, 2009 at 11:29:00PM +0200, Jussi Peltola wrote:
> Not knowing your network I can only guess you don't want to mix carp and
> OSPF on the "outside" interfaces. OSPF will handle the fail-over.
>
> CARP interfaces listed in ospfd.conf as passive will "just work" and get
> advertised in
On 2009-11-30, stan wrote:
> 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 n
Not knowing your network I can only guess you don't want to mix carp and
OSPF on the "outside" interfaces. OSPF will handle the fail-over.
CARP interfaces listed in ospfd.conf as passive will "just work" and get
advertised in OSPF when they are master.
You probably don't want redistribute connect
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 {
> int
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 anot
I have a pair fo redundandt firewalls, using carp that i have recntly
upgraded from a raelly old version of OpenBSD (actually replaced, I built
new disks for these). I read that 4.6 would allow me to set up OSPF such
that it would advertise the shared address provided by carp. So, I have set
things
12 matches
Mail list logo
