+1 I totally agree. From my non developeer point of view, it seems to be the best way to have secure upgrade on embedded. And if a flash goes wrong, simply plug your console cable and choose the other boot option! If we want to save our RRD graphs, we must have them on the config partition too. Devs, is there a problem with this solution? (except time :) )

After much time perusing my Award Bios I finally got DMA turned off and now I have it installed and running. Thanks for the push!

Thank you for the quick post. I was under the impression the GUI was a default option. Thanks again for your help.

hi i have the same issue with different 8 brand routers, it only worked with static ip on wan side of pfsense box, but i finally i configured my routers as bridges only, so my wan takes its IP from ISP, all pfsense boxes working like charm, and i am accessing all of them from wan and controlling all of them from home and from my work hadi57

Check the 1.2.2 release announcement. http://blog.pfsense.org/?p=351 To get notifications of updates, send a blank email to announce-subscribe@pfsense.com

I'm not sure that's the case, if I reboot the pfsense box (after getting the NAT working), I need to preform my procedure as mentioned in my last post..

The speedtouch should still have an IP. This will probably help you access it: http://forum.pfsense.org/index.php/topic,5727.msg34562.html#msg34562

If you want to, you can change the BIOS to match by pressing 's' during the memory test.

Still broke in 1.2.2, for me anyway!

With my cable provider it can take several hours to update changes and the connection becomes active again, just leave it connected and switched on overnight. If its the mac address causing the problem you can enter the old mac on the WAN interface of pfsense box.

Yes, I reached the bootloader and was even able to use the menu option to reboot. But that's how far it went no pfsense unless the serial cable was not connected during the first 2/3 minutes, and also only on the 4801 box the 5501 had no problem at all.

Sorry for late reply - yes I adjusted fstab as specified. But, as you say - it appears that Seagate Microdrives have problems… However, would be very interesting to know what lies behind this mystery...

doesent it say after hd install admin pfsense if i recall correct ;)

So that would be a 'yes'. It just looked odd to me, just wanted to make sure it wasn't something weird.

Yep, we're about to release 1.2.2 to address this and 3 other items.

Thanks all for your help, I bit the bullet and got a USB to serial cable.

I had to downgrade (re-flash) to 1.2.0 to have a system that was accessible. Is their any word on a fix for this? The pfSense is installed on a Dell GX240 system. I've had the 1.2.0 version installed for about 10 months now with no troubles and I'm happy with it however I like to have up to date software installed.