Then the redundant IP should be on the carp interface
Are you going to use carp on the external (public) interface ?
In order to use failover, yes.
We are moving from single to dual 3.7 FW's with CARP. The external
interface has a lot of binated aliases and I am unsure if they are to go
i
Then the redundant IP should be on the carp interface
Leo
-Message d'origine-
De : Per olof Ljungmark [mailto:[EMAIL PROTECTED]
Envoyi : jeudi 13 octobre 2005 10:40
@ : Lio Goehrs
Cc : misc@openbsd.org
Objet : Re: aliases on CARP interface
> Are you going to use carp on the
Are you going to use carp on the external (public) interface ?
In order to use failover, yes.
We are moving from single to dual 3.7 FW's with CARP. The external
interface has a lot of binated aliases and I am unsure if they are to go
into hostname.carpN or stay as they are in hostname.ext_i
Are you going to use carp on the external (public) interface ?
Lio
-Message d'origine-
De : [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] De la part de Per olof
Ljungmark
Envoyi : jeudi 13 octobre 2005 10:00
@ : misc@openbsd.org
Objet : aliases on CARP interface
We are moving from s
We are moving from single to dual 3.7 FW's with CARP. The external
interface has a lot of binated aliases and I am unsure if they are to go
into hostname.carpN or stay as they are in hostname.ext_if.
Could someone please enlighten me? Thanks.
5 matches
Mail list logo