Nevermind, idiot here.  Came home, plugged it all togther properly, disabled dhcp on linksys, enabled it on pfSense and I'm srfin from home ;)

Thanks again all

-Marty

Today I remotely upgraded our primary firewall to 1.2.2.  It didn't came up anymore.  I went to the datacenter and it was just hanging in the boot sequence.  I have taken some information and will verify this tomorrow with the vendor.  As the bios version is the latest.

So it is definitely a problem with freebsd 7.x and supermicro hardware.

Thanks everyone

I'm using pfSense-1.2.3–20090718-2234-nanobsd.img.  Would I be right in thinking this version will default to vr0 and vr1?  I have tried connecting to each of the 3 ethernet ports and it appears DHCP is not active as I get no IP address.

Elliot

ahh sorry i mixed up the story :P

WAN was 62
lan was 192.168 numbers sorry to mislead you.

the poblemen was the NIC i had an other old one. and now everything works ;)

We had the same problem. Changed to Intel NICs and it has been running for 6 months now.
Check your hardware.

Well I've tried different NICs, problem is still there. Tried to install pfsense using the same CD on P45 mobo,works fine, tried installing Freenas on the same PC that didn't work with pfsense, Freenas installs just fine. I guess Pfsense doesn't support this mobo..

I can also confirm the patch works. No more kernel panic when rebuilding/degraded RAID. Tested with 1.2.3-20090623.

Thank you, jimp!
:)

@jahonix:

You seem to have an IP conflict.
Your Linksys router AND your pfSense both have the IP 192.168.1.1 - which doesn't work.
Using a switch seems to be the easiest to solve this. Don't connect the router at all.

Okay, seems to be a simple solution. What I figured, thank you.

I'm going to be needing wireless however. But i'll cross that bridge when I get there. I think it's just a matter of adding a new interface and plugging in the router, I'll research more.

Thank you  :)

I finally got it to work  ;D ;D ;D ;D. I re-burnt the disk at a slower speed.