Like most cheap "RAID" controllers the Promise card is little more than a dual port SATA controller - the mirroring is handled by the drivers Promise provide (also known as fake-RAID).

Got it. Thanks

@jimp: It might be crashing during the boot process. You might try to disable some things in the BIOS as a test, such as ACPI Or try some of the many other suggestions here: http://doc.pfsense.org/index.php/Boot_Troubleshooting cool after disabling the ACPI it work's fine :) Thanks

After chastising the new addition of the PFsense box into a network that previously worked un-flawed, I have finally located the intermittant problem (everything works when I attend site). One of my access points which has sat happily for years on the network without the PFsense box decided to give up - it would allow wireless connections but no IP from the PFsense box could be issued as the LAN side of the access point would not work. Another case of hardware issues.

@Efonne: Those NanoBSD images currently only use a serial console and do not have VGA support. That was, of course, the problem - thanks a lot! Probably it would be nice to document that on the Download and Versions pages.

There are no publicly available scripts that I'm aware of. It shouldn't be too difficult to do it line-by-line by hand, however.

No - you don't need to have any network cables connected. Can you provide: The exact version of pfSense you're running (eg 1.2.3-RELEASE nanobsd) Exactly what the problem is (so far, all we know is "it doesn't work")

I currently have two ALIX 2D3 running 1.2.3 Released with no problems.  I would try reflashing with 1.2.3 and if the problems still persists, save the aluminum case and throw the motherboard in the trash.  BTW, have you tried another power supply? Roy…

Thanks jasonlitka. Looks like that is it then…. Looks like it won't be in FreeBSD 8.1 either (pfsense 2.0).... Time to go and buy another NIC (or look at another FW disty) Thanks all for quick response to my original query.

I can share my config with you, although… some call it overkill  :o I run pfSense in a Vmware ESX enviroment, and therefore have access to quite a few virtual NICs (which is nice for segmentation and VLAN purposes). This is the vlan-config running inside vmware : http://0o2471.net/15677 And this is what the physical cabling looks like : http://0o2471.net/15653 The VLAN 200 is a isolated connection to my DSL-modem, incase I need things to have direct access (official IP's), and if I put a host in this VLAN it will get a DHCP from my ISP. The VLAN 300 is my internal VLAN for regular connected laptops \ computers that I trust, I'm thinking of implementing a auth of some sort for this VLAN. The VLAN 400 is my Wireless Guest network, the host connected here have no access to the internal network, but talk only to pfSense and the internet, there is also a captive portal here The VLAN 500 is my Wireless internal network, where I myself and other trusted computer connect, same priveleges as VLAN 300, but this SSID is hidden and WPA2-protected, also my IP-telephone is on this network The VLAN 600 is the management VLAN on which only managementstuff is, like the Switches, accesspoints and iLO of the servers This is btw only my lab :P

OK, managed to fix it, although not sure how. I just tried different combo's from the documentation on boot up issues and it finally worked…

You might be able to have the best of both worlds if you setup your keyword filtering software on another box (in a DMZ, perhaps) and then forward web traffic through it. Keyword filtering is rather expensive in terms of CPU, it would probably be better on its own box anyhow. I know some people have setup a separate server for something such as DansGuardian to use as a local proxy.

Hi Jonny, Actually I have a pfsense box running on Citrix XenServer 5.5, I got the same error when I ran VM. To fix this simply I downgrade my Bios version from computer. I dont know if this issue will fix yours but is a way. Regards, Heitor Lessa

You gave me some ideas…. and i found the problem.  On our DNS server we were using C Names to point to our thirdparty sql sqlserver, but that record had been deleted sooo the sql connection call didn't know where to go (actually it was calling the wrong server).  I put the C record back in... and we're good to go. thanks for your help! Rookie mistake on my part!  :( :)

I replicated the same exact setup after installing pfsense 1.2.3 and it seems work well. I guess there was some error in system files since the box was shut down few times not properly - just guessing.

when using non standard ports over http/https you have to specify the port with :xx, replace xx with port number, this overrides the defualt port number for that protocol (http=80, https=443). Thats why if you could ssh into it, i figured it was something like that (especially since you said it has to be easy) Glad I was able to spare you the trouble.

this is all you will need: http://192.168.1.1 Internet should be DHCP, LAN should be 192.168.1.1 http://doc.pfsense.org/index.php/Tutorials http://doc.pfsense.org/index.php/Main_Page

Thank you both for your assistance, I'll track down a serial cable and install it that way.  Your advice is appreciated.