From the WEB GUI: Interfaces -> WAN, scroll down to Static IP Configuration, use the pull down menu to adjust the number of bits in the network mask, scroll to the bottom and click Save, then click Apply changes.

Many thanks for your reply. It is what I was thinking of. It is strange I made a search and did find this particular thread….

@jimp: Not sure what it might be then. Is your BIOS up to date? I have FreeBSD 8.1 amd64 (same as pfSense uses) installed on my workstation which boots from a 1TB drive and has 8GB of RAM. No problems at all. I don't have a spare 1TB drive to try pfSense on though. Some BIOS implementations won't boot from a partition that large. Though my root (/) slice is only 2GB and I have slices setup for other things (/tmp, /var, /usr, etc). I forgot to mention that in the first place i did suspected that the Bios not updated and i did update it , it didn't change the situation. you suggesting to slice it acutaly i managed to install it with freebsd distribution cd and slice the disk into 4GB where all are installed,another 4GB EMPY ,rest of space also empty then i installed it on the first 4GB with 2 November version i got. i have question would it be issue to have only 4GB drive  ,otherwise would it be possible to redistribute /tmp etc.. actual to other location without reinstalling? Thanks

Thank you all for your advise and time. [SOLVED] Best wishes.

I'll answer my own question.  I tried rebooting, and updating the snapshots before yesterday and nothing. I updated to the latest snapshot Saturday 03:00 snapshot and low and behold the CPU usuage started working. Great stuff!!

I looked but I dont have it here…  Im going to look at my office machine later to see but I may have to start fresh and try it over... But this is from that time frame... http://forum.pfsense.org/index.php/topic,29333.msg154227.html#msg154227

It really depends on the quality of the media. Some can last for years, some will only last a few months. It's pretty much a crap shoot.

@RpR: You can install pfsense from usb. See the sticky on top: http://forum.pfsense.org/index.php/topic,28264.0.html cheers, i tried that and it worked perfectly

@BlueToast: Problem solved! FreeBSD didn't like large capacities for . That isn't true of FreeBSD in general. You can have a / as large as you want in most cases. Certain BIOS implementations, however, can choke on this.

After I edited a script /etc/inc/filter.inc and it works for me!  8) (here is how should be done - thanks to  savago)

I run a double NAT configuration: pfSense 1.2.3 downstream of a Zyxel ADSL modem. I've tried a couple of times to get the modem into bridge mode to avoid double NAT but haven't been able to get PPPoE to work. I did have some problems with VOIP soft phones but was able to resolve them by careful software selection. Sometimes I run "triple NAT": a test pfSense box downstream of the production pfSense box. Everything works pretty well for me but I don't have a wide range of applications and protocols in use (pretty much basic home use: mostly gaming, web browsing and email with occasional FTP).

Does the pfSense host get a WAN IP from your ISP?  Did you power cycle your ISP's modem? Can you please post, as wallabybob has asked twice already, the output of ifconfig -a.

@wallabybob: That's not the embedded version. It should show boot progress on the monitor. What is on the screen after you boot? Is this the same problem as the similar one you posted in the hardware forum? Its often considered poor form to post the same problem in two different places. There are other people who have posted their experiences with the SuperMicro X7SPA-HF It might be worthwhile searching the forums for X7SPA and seeing what turns up. Someone else may have solved your problem. I connected another monitor and what do ya know, it worked. I have no idea why. I can't explain it. Knoppix and an untangle install worked but some some reason pfSense didn't like the monitor I was using. Bizarre. Anyway, thanks for the help, just glad I am able to install it now  ;D

Forget it all. Everything works fine now. Turns out one of my PFsense devices was glitchy. Reinstalled from scratch and restored the information and it worked fine. I wish there was a way to find out what made it so buggy.

we ended up updating the old slave to 1.2.3-Release then taking a backup of it and dumping it onto the new kit. Made new2 the master and then backed up the the old master, restored it onto the new master checked and we had a working cluster again. Many thanks

You're right on the minimum RAM requirements, which won't help. I'd guess it's probably a hardware fault, but you really need to view the console when it crashes to find out.

@sandman06: hi there could you explain how you ran the install of pfsense from usb http://forum.pfsense.org/index.php/topic,28264.0.html

@amrogers3: Thanks for the reply. I apologize I am new at this and trying to learn. How did you get the md5 hash of the .md5 file?  ??? How do I compare the checksum of the .iso.gz to that of the .iso.gz.md5? I did take the md5 of both files and compared them, I know that is wrong. Calculate the MD5 of the iso.gz file. Open the .iso.gz.md5 file in a text editor (e.g. Notepad), compare the contents to the calculated MD5 of the iso.gz file.

You'd need a MIPS compatible version of pfSense for that.  There is some very early work underway, but from what I can tell it's a long way off.

I would look at the newer model X7SPE-HF-D525 with the Atom 1.8GHz processor and DDR3 memory support.