This problem was solved by enabling the only available power related option in the dell bios.

Flash forward a couple of months… building another pfsense system on new dell hardware, same problem, but now the bios doesnt have ANY power related options to change and I dont see a workaround. Not sure what I'll do. If I figure it out I'll follow up.

I'm using a rt2500 pci without problems. Normal power supply.

Yeah must be a BSD issue.

I'm seeing the same thing with an external USB CD/DVD drive (Philips USB 2.0 SPD3100CC, 16X DVD +/- RW).

FreeBSD 6.2-RC1 acts the same way, so it's not a pfsense issue.

There is a FreeBSD PR related to this, kern/85257. 
http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/85257

Hopefully it'll get fixed in FreeBSD eventually…

I found the problem or at least an easy work around.
If I make fxp0 the WAN and fxp1 the LAN. The pfsense automatically assigns the default gateway to the WAN (fxp0).
It strikes me that this isn't all that intuitive.
I think one of these options (or something similar) should be done:

Modify the setup pages so they recommend you use fxp0 for the WAN instead of fxp1. Modify the rc.interfaces_* scripts so that they set explicitly set the interface when running ifconfig for the default gateway to the interface of the WAN. Modify the UI and the rc.interfaces scripts to explicitly specify the interface for the default gateway.

right.

Bridged interfaces in pfSense support STP too and as you can configure pfSync independently from carp the first solution from that doc might be doable with pfSense though you still need a fake IP for the WANs. If you test this let us know how it works.

Thanks for the feedback. This board is great!

I'd like to be able to administer the firewall remotely (including updates), so I guess a hard drive version is still the easiest way to go.

Whenever FreeBSD 6.2 is released.

Thanks for the quick response. I'll test it out either this week or next.

things have changsed mutch sins then
the beta's where on freebsd 6.0
the rc's and 1.0 release and 1.0.1 are on  freebsd 6.1
the snapshots you can download now are freebsd 6.2 beta

even on this version with freebsd 6.2 it still always detects sis0 or sis1 interface alot even if it doesnt exist. and on this version i get some errors when i partition and install to hdd. just trying to give some info about this version. if u all wanna know the error msg i can post it here. thought it works just fine

the CRC error is ok.
But i got this error on another installation too, but after that it worked fine.

So any more ideas? :)

Thanks for that I was trying to avoid having to take the firewall apart to change this box to PF

guess I will have to take it to bits then

and 3)  -> OK then. Is enough for my test.

tnx a lot

pfctl: DIOCSETSTATUSIF indicates a interface is present in the XML configuration but for some reason PF is not seeing the interface.  You may want to reset to factory defaults.

Did you try a biosupdate?

@Imajica:

@jeroen234:

setting a proxy server you do in youre internet browser

Ah.  Then pfSense won't do what I need it to do…

Yes, it will. What he's saying is that you just need to set the proxy option in the browser, not at the router.

I'm beginning to think Squid had something to do with it.  Since uninstalling Squid, I haven't had any lockups.  I'll report back with log excerpts if this changes.