OK Thank you! I tried change to enhance mode, but also without success. In an next step I will try with smaller partitions.

@impire: I think the problem boiled down to using the 2 NICs of same exact model. This will conflict with the built-in NICs as  Pfsense or FreeBSD seems to assign the same IRQ to both NICs. Its very unlikely that interrupt sharing is a problem for modern NIC drivers. When I saw multiple bce NICs, problem on enabling fourth, I immediately thought of the page Steve linked to. It seems the bce driver preallocates a lot of mbufs (network buffers) on enabling a NIC and this causes causes exhaustion or near exhaustion of the default mbuf allocation when there are "enough" NICs.

@jimp: http://doc.pfsense.org/index.php/What_are_the_512M,_1G,_2G,_and_4G_NanoBSD_files%3F thank you.

You can download that upgrade.img.gz file and apply it from System > Firmware. That upgrade image would not require a "reflash" from 1.2.3 there, it upgrades in-place via the GUI (or console update), and retains your configuration. If you want to wipe the card and reflash starting with 2.0.1 you would need the full image (it does not say upgrade in the filename), and that would not keep your config you'd have to take a backup before starting, and then restore that config backup after booting the newly imaged card.

Package reinstall probably failed. Check the console. You can clear the lock by going to Diagnostics > Backup/Restore and hitting the button at the bottom to reset the lock. Then you can reinstall the packages you need.

It already checks the availability of the package server before it starts the reinstall process. However, if a package pulls in data from a different server than where the package's main files come from, it can fall into a different kind of trap there. There are probably ways to make the whole process more robust, but there isn't an easy way to redesign the whole process to download all of the files first and then reinstall.

Some more information might be helpful: What variant of pfSense (nanoBSD, full, full embedded)? What motherboard? What else is displayed on the screen (or serial port)?

Update worked fine on the first site but failed on the second site, reinstalled using the full install ISO (i386) but I am faced with the same issues, packages wont reinstall also I have X3 WAN's using PPPoE and the third WAN keeps disconnecting  :( Now reinstalling Version 2.0

@johnnybe: @pfsparc: Today I did a reinstall of pfsense.. All went fine, until Snort was fired up, and the http inspection issue arose again. Suppressing it doesn't help. So for the time being '-1' helps, but will have to look into this more coming days. bdwyer says: Make sure you add your suppression list to the snort interface settings.  Change it from default to the list that has that rule. http://forum.pfsense.org/index.php/topic,43043.msg222725.html#msg222725 It works, as you can see here as well: http://forum.pfsense.org/index.php/topic,43606.msg225992.html#msg225992 Many thanks !! As the second link gave the real hint… adding the suppression list to the snort interface.

Yes I am running NanoBSD version. I see so it's like a backup version… that's very clever and I'm sure very useful in the event of problems or for testing. Thank you for clarification. :)

Apologies to all - did not intend a hijack Andrew

Presents the same message above and have worked with the steps for manual installation of pfsense in HD, but the problems persist, I think it should be the 32bit version. I did the test with 64bit.

follow instructions on this topic to fix it: http://forum.pfsense.org/index.php/topic,44224.msg229418.html#msg229418

Will check tomorrow - time to go home here

Problem resolved.  From my notes: To edit fstab on embedded flash: On separate machine, Boot into pfSense from the Live CD Do not select Recovery or Installation options, let the system boot until the menu appears Pick option 8 to drop into a pfsense shell prompt From the shell mount the CF which is likely /dev/da1s1a to /mnt Proceed to edit the /etc/fstab file to reflect the correct device ad0s1a NOTE: The fstab file indicates that the drive is to be mounted rw.  Is this correct?  Also, I think I killed the swap install onto the flash card by specifying 0 bytes for swap space size. SUCCESS!!  This process seems to have worked.  fsSense booted up fine.

That's exactly what I thought, 'DHCP comes before IP and TCP surely'. Wikipedia is never wrong!  ::) Steve

If you need to know what the default cron jobs are (if they were deleted or altered), they can be found in the default config located in /conf.default/config.xml on the firewall.