@gonzopancho: I'm actually looking at using ZFS to do this, rather than the 2 slice nano setup. ZFS let's one keep multiple copies, and provides transparent compression on/off the SD card. First I have to prove (internally) that it is as reliable. @gonzopancho: As above, I'm investigating running ZFS as a first step to moving on from the nanobsd past and its restrictions. If it pans out, then likely that a "3.0" version of the pfSense software will run something a lot like 'freebsd-update', rather than the BWOS-like releases of today, and likely also something a bit more modern for a configuration system and GUI than the large mass of PHP that defines the product now.  This should help us address some of the security shortcomings in the current codebase. NO decision has been taken (yet), it's just time to re-think the direction. +1 for ZFS

It is the Delete key that is used to enter the BIOS. However, several of the F keys do work once in the BIOS, like F10 to save and exit. I didn't have any problems using Putty 0.63. One point that might be worth mentioning aout these boxes, is that the front panel lists the rightmost port as 0 Internal and the port to its left is labelled 1 External. However, when setting up Pfsense for the first time, the rightmost port ( 0 Internal ) is msk3 and the port to its left ( 1 external ) is msk 2. I found this out after setting up msk0 and msk1 and thinking they were the ports labelled 0 and 1 on the front panel. I couldn't understand why my pings were failing! All sorted after a cuppa  :)

Removed a couple links here, one that was not something to write out in the way instructed, one that won't exist much longer in that location. If you need to re-flash any hardware you purchase from us, please get in touch with us via your bundled support and we'll be able to point you to the correct image.

You have reinstalled the packages after the upgrade? Sometimes removing them and reinstalling them solves issues that merely reinstalling them (without removing them) does not.

You could disable one of those by editing the config file directly and then reloading it. Be aware that getting it wrong or typo'ing something can result in the box not booting or some other unwanted effect! Steve

@priller: What is your Internet?  Cable modem?  Is pfSense pulling a WAN IP address? If CM, you need to power cycle it if you change the attached device and the MAC address is different. Yeah I'm an idiot and didn't even think about the fact that the WAN needed to get a new public ip from my ISP. I gave it no time to do that and I'll try power cycling it when I get home. Thanks

I'll give it a try. Thanks!

There was a great post about that in 2008: https://forum.pfsense.org/index.php?topic=8273 It's a pity it haven't got enough attention.

Yes, modern SSDs shouldn't be a cause for concern. Though you can still use that /tmp and /var option if you want to be extra kind to the disk.

@stephenw10: This should work pretty much 'out of the box'. Try swapping the WAN and LAN NIC assignments or using the on-board Gigabit NIC for LAN. When you use DHCP is the client receiving an address? Steve The machine in question is now in service with IPFire, so I can't test at this time.  However, I tried pfSense on another PC, configured like the first one, and I had no problems accessing the web interface.  At least I'm able to evaluate pfSense now, but there seems to be some hardware compatibility issue with the first system.  If/when it gets pulled from service, I'll give it another try with your suggestion (using onboard Gb for LAN). Thanks!

I had updated the the latest BIOS prior to the install.  I've looked to see if I can disable ACPI in BIOS and haven't found an option yet.  I think I might just RMA the MB back and get another to see if that will work better.

It appears the image you have on the USB stick is one of the the Nano images, yes? There is no option to install from there, it's not intended to be install media. Will it boot from the memstick image on a USB stick? That will give you the option to install the 'full' version of pfSense. I would still try to run Nano from a DOM though. Others have run full with no issues. Steve

@stephenw10: @stephenw10: Hmm, confusing indeed. It looks like the console itself is not failing rather the shell is. The only vaguely similar thing I have seen is where the menu fails to spawn completely at the end of boot and you're left with no prompt at all. There were a few workarounds in that case. One was to simply change the serial baudrate. Seems unlikely to make a difference here but it's an gui setting now so an easy test. For example: https://forum.pfsense.org/index.php?topic=34814.0 Could try running at the #: /etc/rc.initial Not entirely sure what that might do to an already running system so probably best not to do it in 'production'! Steve I previously had the baud rate set to 9600 (default), but my ALIX BIOS uses 38400 … so a few weeks back I switched it to 38400 on pfsense as well. In my case the menu does spawn on boot, but dies some hours later.  Each time (in this thread) I've said I rebooted my ALIX, I did verify I had a workable menu on the serial console. I just tested running /etc/rc.initial from the serial console ... which so far appears not to have any ill effects (though I'm typing this up a few minutes after running it!).  And restores the serial console menu. [2.1.5-RELEASE][admin@fw0.localdomain]/root(4): date Sat Oct 11 18:17:45 EDT 2014 [2.1.5-RELEASE][admin@fw0.localdomain]/root(5): uptime 6:17PM  up 25 days, 19:33, 2 users, load averages: 0.00, 0.00, 0.00 [2.1.5-RELEASE][admin@fw0.localdomain]/root(10): ps auxff | grep rc.init root  83274  0.0  0.6  3644  1512  u0  I+    6:11PM  0:00.02 /bin/sh /etc/rc.initial root  36527  0.0  0.4  2444  1060  0  R+    6:21PM  0:00.00 grep rc.init root  80618  0.0  0.5  3644  1320  0  Is    6:11PM  0:00.02 /bin/sh /etc/rc.initial @MaxPF: @MaxPF: <…snipped...> I removed [SOLVED] from the title. Thanks Max! I'll continue to use this thread at this point.

@Rewt0r: The firewall was rejecting the packets until I forwarded the packet using a forward rule even though I already had a firewall pass rule and a nat 1:1. Then your firewall rule was wrong, NAT applies first, private destination is probably what you missed.

sorry… the script is /etc/rc.initial. Change the shell under option 8 to bash.

To me, its not clear what you are asking? If you are asking can pfsense be ran as a VM in any of those OSs you listed, the answer is yes.  All of them, under vmware.

Well, I figured it out. I was using a usb ethernet device with the MCS7830 chipset, that I had to load the kernel module to get recognized.  From here: https://forum.pfsense.org/index.php?topic=50241.0 It did recognize it, I could configure it and everything, but it just didn't work.  I pulled an old pci ethernet card out of the junk box and now everything works just fine. thanks everyone

details can be found here: https://redmine.pfsense.org/issues/2770

@imanz: I just wanted to let you know that it is working correctly after the change. Thank you for the quick response. Not that install and basic configuration is complete I will move on to correctly setting up all the subnets; will probably be back with more questions :) An OT question. Since I just installed pfSense 2.2.Beta on a similar set up, same board, same amount of RAM but using an INTEL S3500 SSD 80GB. I am using a M350 case, 1 Noctua Fan (40x40x10) blowing from the upper case directly to CPU and RAM. Can you kindly report your operation temperatures, case used and fans (number, position and flow direction)? Thanks

Firewall Log DNS Lookup Dialog Box Missing in 2.1.5 https://forum.pfsense.org/index.php?topic=81145.0