I have never ever seen a box just all of the sudden stop working.
Now you have :)
Maybe I missed the point you were trying to make here. I am sure it stops
passing traffic to my DMZ (OPT 2) interface and I am also sure that the GUI
and SSH continue to operate. Additionally I am sure that /etc/rc.bootup at
the shell does not change anything at all once the machine is in this state
and that only a reboot brings it all back.
As for console messages, I have not been in front of the machine at the
console to see if there were any.
This has happened twice so far, the first time after 4 days of uptime and
the second after about 4 or 6 hours of uptime (can't remember exactly).
Todd
----- Original Message -----
From: "Scott Ullrich" <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Wednesday, September 21, 2005 11:33 AM
Subject: Re: [pfSense Support] Argg! My PfSense just died!
top from a shell will tell you this.
I have never ever seen a box just all of the sudden stop working. If
a box blows up, it goes big time with kernel panics, etc. And even
this I have not seen since being on crappy 5.X. 6.X of FreeBSD is
looking mighty fine.
Scott
On 9/21/05, Mojo Jojo <[EMAIL PROTECTED]> wrote:
I meant, nothing plugged into the LAN NIC and nothing plugged into the OPT
2
NIC.
Sorry about that.
I am starting to wonder if this could be a RAM issue, as in, not enough of
it.
Todd
----- Original Message -----
From: "Chris Buechler" <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Wednesday, September 21, 2005 9:19 AM
Subject: Re: [pfSense Support] Argg! My PfSense just died!
> Mojo Jojo wrote:
>
>>
>> Just some further info..
>>
>> System died last night again after approx 6 hours of uptime.
>>
>> I could still get to the GUI, could still SSH to it but it would pass
>> any
>> traffic through to the OPT 2 (DMZ) interface.
>>
>> I attempted to run /etc/rc.bootup at the command line which restarted
>> Pf
>> fine. After the restart of Pf (not the whole computer) everything thing
>> was still in the same shape with no traffic passing through to the DMZ.
>>
>> The only thing that corrected this was a reboot which I initiated via
>> the
>> Pf GUI.
>>
>> Further info:
>> V. 0.84
>> Running on a PIII 933 with 128mb of ram. I have 4 Linksys NICS
>> installed
>> on the PCI bus and one on the motherboard which I had disabled.
>>
>> Onboard NIC (disabled in BIOS)
>> Linksys NIC 1 > LAN
>> Linksys NIC 2 > WAN (static IP on a T1 with ascend T1 router on other
>> end)
>> Linksys NIC 3 > OPT 1 (DMZ where servers are)
>> Linksys NIC 4 > OPT2 (not in use at the moment)
>>
>> The PC is a DELL, Pf is running on a Hard Drive.
>>
>> I installed a fresh copy of 0.84, this is not an upgrade.
>>
>> All Linksys/Network Everywhere NICS are identical model NC100.
>>
>> I have 26 aliases setup, 46 rules on the WAN tab, 14 rules on the DMZ
>> tab
>> and none on the LAN or OPT 2.
>>
>> I have nothing plugged into the WAN NIC and nothing plugged into the
>> LAN
>> NIC at this time.
>>
>
> umm, above you say it stops passing traffic, here you say you only have
> one NIC plugged in? It can't pass traffic with only one NIC plugged in.
> system logs after it stops passing traffic if it happens again may prove
> very useful.
> -cmb
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
