On 8/27/05, Scott Ullrich <[EMAIL PROTECTED]> wrote:
> On 8/27/05, Bill Marquette <[EMAIL PROTECTED]> wrote:
> > Oh, you will have to reboot after mucking with preempt settings and
> > BOTH boxes have to have it set.
>
> Not on recent versions. I changed the CARP settings screen to call
> both of
On 8/27/05, Bill Marquette <[EMAIL PROTECTED]> wrote:
> Oh, you will have to reboot after mucking with preempt settings and
> BOTH boxes have to have it set.
Not on recent versions. I changed the CARP settings screen to call
both of our carp functions which should set the preempt.
Scott
onality required ifdepd .. preempt results in the
> > same behavior?
> >
> > - Original Message -
> > From: "Bill Marquette" <[EMAIL PROTECTED]>
> > To: "Matthew Lenz" <[EMAIL PROTECTED]>
> > Cc:
> > Sent: Friday, August 26, 2005 7:00
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
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:
Sent: Friday, August 26, 2005 7:00 PM
Subject: Re: [p
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 th
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 Marqu
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 ou
I think it _might_ be because that bge0 is sharing an irq with one of
the usb controllers. I'm going to disable as much of the onboard stuff
as possible that I have no intention of using. (usb is one of them)
On Fri, 2005-08-26 at 10:11 -0400, Scott Ullrich wrote:
> Intel Intel Intel Intel.
>
>
Intel Intel Intel Intel.
Really, use Intel.
On 8/26/05, Matthew Lenz <[EMAIL PROTECTED]> wrote:
> On Fri, 2005-08-26 at 01:50 -0400, Chris Buechler wrote:
> > On 8/26/05, Matthew Lenz <[EMAIL PROTECTED]> wrote:
> > > The watchdog (atleast thats what
> > > the system log called it) on my WAN inter
On Fri, 2005-08-26 at 01:50 -0400, Chris Buechler wrote:
> On 8/26/05, Matthew Lenz <[EMAIL PROTECTED]> wrote:
> > 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?)
>
> various reasons. I have s
On 8/26/05, Matthew Lenz <[EMAIL PROTECTED]> wrote:
> 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?)
various reasons. I have some Broadcom gig NIC's (bge) onboard on Dell
2550 servers that like t
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
13 matches
Mail list logo