Thats FreeBSD installation. pfSense installation is different from FreeBSD installation. For pfSense installation go to the pfSense home page and follow the documentation link to the documentation Wiki and/or the Tutorials and you will see both Tutorials and Wiki articles on Installation (and other topics that are likely to be useful).

Ok.. SO

ive managed to re-format my CF's back to their normal size, and after installing XP on a machine wrote int .img's to a few CF's.. but now.. when i plug in the bios update CF and power up i get this error:

also when i plug in a pfsensenanobsd i get " Boot 1" and then a whole lot of ############### down the screen… any ideas?

Solved

Need to upgrade de BIOS before installed on CF card

I've used a 1GB DOM for a couple of years without apparent problem. 2GB may not be enough if you are planning to use packages that are heavy disk users (e.g. squid).

I suspect you could see filesystem problems if you get a powerfail while the configuration file is being updated. I have seen file system problems and configuration file corruption when pfSense 2.0 BETA was panicing when rum devices were enabled.

We're not load balancing though.  We are just moving from a weaker server to a real strong one.

I've moved configs many times like this and I've not had an issue before which is why this so strange to me.  I may just have to rewite config from scratch…didn't want to because it is rather large.

@cmb:

You can't easily modify the images to fit in 256 MB, 512 is the minimum supported. You could hack the build scripts to build your own single slice 256 MB version but it's not worth the effort, unless you want to spend probably 50 hours figuring out the build scripts and how to change things around. A 512 MB DOM is $30-60 USD roughly.

Its actually less about money and more about fun and walking tall after wasting few hours!!!

I have a 300mhtz fanless machine with 256mb ram and 128mb flash.

I successfully flashed Embedded 1.2.2.

Now it boots fine and then hangs after a while and its expecting me to configure that from serial console,

Turns out that I don't have access to serial null modem cable and also an available serial port on my laptop.

Here is what I am thinking…...

Take a USB flash drive formatted in FAT.
create a directory \conf
then store a skeleton config.xml file from another machine and edit to give it important stuff like interfaces and dhcp etc... and keep everything else fairly blank.
store it in this usb drive as \conf\config.xml

fire it up to see what happens....

Will this work? Or damage my image. Don't want to go through a painful imaging again.

If it worked, then I can use either a wget on shell or
Diag > Edit file

to create a good copy there and reboot using the Ethernet laptop......

Please let me know. Much appreciate help....

2.0 might be generally safe to use in that situation, but the only way to know would be to test it out for yourself.

1.2.3 would be the right thing to do for most production networks right now though.

You can upgrade from 1.2.3 to 2.0 when it's released, there shouldn't be any upgrade issues when it's released.

I can from today confirm that it works to install it from a remote location without that the pfsense will not lose the config

Finally, I got pfSense deployed successfully in our hosting site!! Thanks for such a wonderful pcs of software! Oh and the book helps a GREAT deal!!

Some time ago I bought a number of USB adapters for note book drives. Some worked with FreeBSD and some didn't. I discovered in the FreeBSD sources there was a table for USB devices with "quirks" and code work arounds for the quirks. The devices that worked used a different chip than the devices that didn't and there was no "quirk" entry for either device.

Suggestion: You try to read the whole external hard drive on a "bare metal" FreeBSD system by a command like```

Check any port forwards you may have configured:

http://doc.pfsense.org/index.php/Why_does_enabling_NAT_Reflection_break_web_surfing%3F

I seem to have isolated the problem to the UDMA settings of my CF.
After looking arount in the web, I suspect that I must change something in the boot.conf to enable (or set) UDMA2 for this CF.
The problem is .. how do i do something like that ?

It was actually McAfee personal firewall causing the issue. I thought I had it configured to accept incoming ICMP but somehow it got reset when I changed my LAN network configuration. I was looking for the root cause to be harder than it was. I guess that's what you get when trying to troubleshoot at 2:00am on a few hours sleep.

I am a N00B when it comes to packet sniffing technologies. I love the features of PFSENSE so far. After reading I'm taking this dumb mistake to learn how to use tcpdump to analyse where my packets drop. I also ordered the "PFSENSE definitive guide" from Amazon. Should be coming in today. Hopefully it can help me understand how to securely setup my DMZ.

Regards,