I too have the "disk is dirty" messages during boot on a standard pc with 256 mb CF (platform set to embedded) this looks scary but everything's performs OK

You shouldn't run different Accesspoints at the same channel (not even if they share the same SSID and Settings). Everything not at least 2 channels away is influencing each other and will cause impact on throughput though it will work.

Thanks Hoba.

Writing a 64 mb partition to a 128 mb card will work as well. However you might want to try the latest snapshot as these images are 128 mb by default: http://snapshots.pfsense.com/FreeBSD6/RELENG_1/embedded/

Thankyou Sai, I will try that soon.

ok thanks hoba for the point for download looks like a good improvement from 9 months ago.  Look forward to seeing it stable.

Thanks Again hoba,   But still no go :( My Loader.conf looks like this :- autoboot_delay="10" hint.acpi.0.disabled=0 But when boot the Box using option 1,  It crashes with a general protection fault when load the network card drivers.  If I use option 2 it boots fine.  I'm just concerned that if the power goes down,  the box will not start unless there is someone here to select option 2 :) Thanks for your help Knotty

Sounds like a DNS Issue maybe? If you can reach the modem you can pass through pfsense.

@guybrush: i know this how-to… but he is physdiskwriting the .gz-archive onto the flash, can this be true?? Yes, physdiskwrite is smart enough to handle .gz's directly  ;)

Thanks for the info.  Currently got the HD hanging out the side of the case and that is working (connected via ide) but clearly this is less than ideal.  Oh well seems like that will have to do for now.

It's unsupported but should work. Use an IDE-CF-Adaptor to move a full install over to the cf-card. When it asks for swap partition delete it from the autogenerated partitionlist. After you finished the install change the  file like sai told you and reboot.

This kind of config is not supported by the frontend currently. There are some anonymisation services that work similiar to this setup. Maybe a bounty would raise some devs interest in implementing this cleanly in the frontend.

I had nearly the same experience just a few minutes ago, only it wasn't a power issue. I was testing failover (CARP) and the backup unit wouldn't pick up the IPSEC tunnels.  I brought the main unit back up, rebooted the secondary unit and it started asking for the password. The secondary unit is definitely FUBAR.  Maybe it's just old and tired and wants a dirtnap?

Memtest on the memory and fsck on the disk. If the checksum checked out on the ISO, and it was verified.

Can I just say that this thread has single handedly fixed my setup problems with pfsense. lol, I was typing in x10 over and over, and I couldn't understand why it wouldn't work… xl0... doh!!!

@Superman: Check here: http://snapshots.pfsense.com/FreeBSD6/RELENG_1/updates/ Ty  ;D

Thanks, I acctually saw that in loader.help right after i posted that. FreeBSD  is starting to come back to me :)