Any reason you're using 2.0-release? That's old! There are a large nuber of threads about how to get past 'stuck at 38%' if you find that an issue. Some people found it eventually went past it others recommend disabling and CPU virtualisation features and any multicore features in the bios during the install. They can be re-enabled for normal running. Steve

To anyone that has read this and might have ran into the same issue… The auto detected IPV6 network IP addresses that were assigned to the interface didn't have a gateway that was reachable and so apinger was going bananas trying to constantly reload the configuration. When I disabled iPV6, utilization went back to normal and re-enabled and properly configured the IPV6 addresses on the WAN it fixed the issue... Hope this is at least helpful to someone else as the logs are not very clear as to what's happening.

So it is now online - this connection is setup by the pfsense vm. I preset all the forwarding rules while the router was not connected to the internet but was connected on the LAN side to an open IP address. To put it online I removed the LAN and WAN connections from the old router. Plugged in the WAN line into the unused but configured interface and turned on DHCP and moved the LAN gateway from the open IP address I used to do the configuration to the same IP as the old routers Gateway.

here is an update. I can now ping out. - however, the ip is 70.177.0.29 the static ip for the wan. when i try Virtual ip, i get nothing. - I cant use the lan, as i have voip phones on there, that requrie an ipsec connection to a remote switch, and they need a public ip address. - So i thought i try a dmz, or use the opt2 as the cidr block. thanks,

http://snapshots.pfsense.org/

I'd read that for the LEDs and Thermal Sensors, but not for the reset button.  Oh well.

@Stewart: I was actually able to fix the problem, I think.  Instead of resizing partitions, we are able to increase the size of the RAM drives.  While this may result in the loss of virus definitions and such on a reboot, it only takes about 4 minutes to be fully operational. Ok, that would work too.

Seems you have to use /sbin/reboot as mentioned below to reboot FYI - it should /sbin/tunefs -t enable /, not /sbin/tunefs -t / as mentioned below. @spid: @dstephens80: Charlie, I will give v2.2 a try and let you know how it goes.  As far as dmesg, I can provide nothing as the system will not boot with AHCI enabled.  it will not detect any GEOM devices, but it will boot fine if I remove the ahci_load="YES" from /boot/loader.conf.local. Did you convert fstab to ufslabel before adding ahci_load="YES" ? Run the following script to do it: /usr/local/sbin/ufslabels.sh then if it boots correctly go in single user mode and enable TRIM with: /sbin/tunefs -t / reboot with: /sbin/reboot and after a reboot check if it's enabled with: tunefs -p /

Log into your server, try to ping something external. Note the actual error given if it fails. Try to connect to the server from some external address, check the server logs to see if those requests are arriving. Steve

The default firewall configuration is to block everything on the WAN so you won't be able to connect from the WAN side. To connect to the webgui you should connect a computer to the LAN interface. pfSense will, by default, be running a DHCP server on LAN so it should give you an address in the 192.168.1.X subnet. Your LAN NIC is an older 10/100 Realtek type so it won't have autoMDX. Depending on what you connect to it you might need a switch or a cross-over cable to connect. You would know right away though because you'd see no link lights on the NICs. Steve

Jason: It turns out that, no, the SATA-DOM isn't operating on pin 7 power and needs the power cable to run on the Supermicro motherboard. Everyone: By Jove, I did it!  I used the iso of a cloning program called "Clonezilla" via IPMI's virtual media utility to copy the content of my old USB drive to my new SATA-DOM.  Thanks to all for your help–in particular to Stephen.

Steve, i will have a look.. i have a feeling it is just reporting it wrong because it appears to be working but I will have a look in the logs..

My box has 1 GB, /temp and /var set to 60 and 80MB, respectively.

@Jason: Do you have the appropriate Outbound NAT rules setup for the second connection? That was it. Thank you. Couldn't see the forest for the trees.

In which case the pfSense box must be connected directly to the WAN connections so it has to go in front of the UTM device. Did you find out what that is yet? Steve