Oh, you will have to reboot after mucking with preempt settings and BOTH boxes have to have it set.
--Bill On 8/27/05, Bill Marquette <[EMAIL PROTECTED]> wrote: > Per 'man carp' > > net.inet.carp.preempt Allow virtual hosts to preempt each other. > It is also used to failover carp interfaces > as a group. When the option is enabled and > one of the carp enabled physical interfaces > goes down, advskew is changed to 240 on all > carp interfaces. See also the first example. > Disabled by default. > > --Bill > > On 8/27/05, Matthew Lenz <[EMAIL PROTECTED]> wrote: > > Scott mentioned that functionality required ifdepd .. preempt results in the > > same behavior? > > > > ----- Original Message ----- > > From: "Bill Marquette" <[EMAIL PROTECTED]> > > To: "Matthew Lenz" <[EMAIL PROTECTED]> > > Cc: <discussion@pfsense.com> > > Sent: Friday, August 26, 2005 7:00 PM > > Subject: Re: [pfSense-discussion] wan interface failed causing carp failover > > > > > > That's why a single interface failure didn't fail the whole box over then. > > > > --Bill > > > > On 8/26/05, Matthew Lenz <[EMAIL PROTECTED]> wrote: > > > not currently no. Mainly cuz I have two firewalls I need to test new > > > versions of pfsense before I can fail it over and upgrade the current > > > MASTER for all the carp interfaces. Once I have everything production > > > ready i'll probably enable preempt again. > > > > > > On Fri, 2005-08-26 at 15:03 -0500, Bill Marquette wrote: > > > > Are you using pre-empt? > > > > > > > > --Bill > > > > > > > > On 8/26/05, Matthew Lenz <[EMAIL PROTECTED]> wrote: > > > > > I had an interesting thing happen today. The watchdog (atleast thats > > > > > what > > > > > the system log called it) on my WAN interface reset the WAN interface > > > > > (any > > > > > idea why that would have happened?) which caused all my outbound NAT > > > > > to > > > > > longer work. All my private gw (LAN/OPT*) carp interfaces/ips were > > > > > still > > > > > MASTER on fw0 but the the public (WAN) carp interface/ip to which I > > > > > bound > > > > > all my outbound NAT failed over to fw1. > > > > > > > > > > Should this have continued to function? > > > > > > > > > > It didn't. I had to disable carp on fw1 to let it the public carp > > > > > interface > > > > > fail back to fw0 (where all the other private carp interfaces were > > > > > still > > > > > MASTER). It almost seems that all the carp interfaces/ips need to > > > > > failover > > > > > if one of them goes down. Am I missing something? I'm sure I must be. > > > > > > > > > > > > > >
