On Thu, Apr 22, 2010 at 7:51 PM, Dimitri Rodis
> wrote:
>>
>> I would really like to see this work reliably at some point. From what I can
>> tell, this problem is not limited to just Fireboxes, >it is on pretty much
>> all NICs that have
>> RTL8139C+ chips on them.
>>
>
>There is something speci
On Thu, Apr 22, 2010 at 17:48, Chris Buechler wrote:
> On Thu, Apr 22, 2010 at 7:51 PM, Dimitri Rodis
> wrote:
>>
>> I would really like to see this work reliably at some point. From what I can
>> tell, this problem is not limited to just Fireboxes, it is on pretty much
>> all NICs that have
>>
On Thu, Apr 22, 2010 at 7:51 PM, Dimitri Rodis
wrote:
>
> I would really like to see this work reliably at some point. From what I can
> tell, this problem is not limited to just Fireboxes, it is on pretty much all
> NICs that have
> RTL8139C+ chips on them.
>
There is something specific about
>On Mon, Apr 19, 2010 at 6:56 PM, Hans Maes wrote:
>>
>> Although it is definately related to the type of NIC's in the watchguard
>> boards, I'm still not completely convinced this is 100% a hardware problem
>> since the Watchguard Linux OS seems to work just fine on it. Sounds more
>> like a Free
On Mon, Apr 19, 2010 at 6:56 PM, Hans Maes wrote:
>
> Although it is definately related to the type of NIC's in the watchguard
> boards, I'm still not completely convinced this is 100% a hardware problem
> since the Watchguard Linux OS seems to work just fine on it. Sounds more
> like a FreeBSD dr
Joshua Schmidlkofer wrote:
Ok new problem: re:1 watchdog timeout. I think we have properly
disabled ACPI. Anyone have any other advice?
Change hardware. Those cheap NICs in the Watchguards have all kinds of problems.
Chris,
Thanks, I appreciate your input. I think we'll ta
>> Ok new problem: re:1 watchdog timeout. I think we have properly
>> disabled ACPI. Anyone have any other advice?
>>
>
> Change hardware. Those cheap NICs in the Watchguards have all kinds of
> problems.
Chris,
Thanks, I appreciate your input. I think we'll take your advice. =(
Weak-sauce
On Mon, Apr 19, 2010 at 4:38 PM, Joshua Schmidlkofer wrote:
>
> Ok new problem: re:1 watchdog timeout. I think we have properly
> disabled ACPI. Anyone have any other advice?
>
Change hardware. Those cheap NICs in the Watchguards have all kinds of problems.
---
>>
>>
>>
>
> Yes, do not blame your switch, something is wrong with your pfSense cluster.
> Most probably your re1 becomes overloaded with traffic.
> Evgeny.
>
Ok new problem: re:1 watchdog timeout. I think we have properly
disabled ACPI. Anyone have any other advice?
Joshua Schmidlkofer wrote:
Does pfSense' log say CARP is moved from Active to Passive?
Evgeny.
Evgeny,
It appears we are getting some of that: (JAX2)
Apr 19 14:48:13 kernel: carp1: link state changed to DOWN
Apr 19 14:48:13 kernel: carp1: MASTER -> BACKUP (more frequent
advertisement re
> Does pfSense' log say CARP is moved from Active to Passive?
> Evgeny.
Evgeny,
It appears we are getting some of that: (JAX2)
Apr 19 14:48:13 kernel: carp1: link state changed to DOWN
Apr 19 14:48:13 kernel: carp1: MASTER -> BACKUP (more frequent
advertisement received)
Apr 19 14:48:10 kernel:
Joshua Schmidlkofer wrote:
I have a site in Jacksonville, FL. We have two Watchguard Firebox
X700s, with upgraded RAM and a pfSense embedded deployment.
Since installation we have had WEIRD problems with the VPN. We
THOUGHT it was the vpn. However, weeks and work revealed an apparent
switch
I have a site in Jacksonville, FL. We have two Watchguard Firebox
X700s, with upgraded RAM and a pfSense embedded deployment.
Since installation we have had WEIRD problems with the VPN. We
THOUGHT it was the vpn. However, weeks and work revealed an apparent
switch problem. Basically, what we
13 matches
Mail list logo
