another update: I loaded the config from the site that worked fine and this is what came up with VERY little delay. Waiting for Internet connection to update pkg metadata and finish package reinstallationUpdating pfSense-core repository catalogue… repository pfSense-core has no meta file, using default settings Unable to update repository pfSense-core Updating pfSense repository catalogue... repository pfSense has no meta file, using default settings Unable to update repository pfSense ERROR!!! An error occurred on pkg execution (rc = 70) with parameters 'update -f': pkg: https://firmware.netgate.com/pkg/pfSense_factory-v2_3_2_amd64-core/meta.txz: No address record pkg: https://firmware.netgate.com/pkg/pfSense_factory-v2_3_2_amd64-core/packagesite.txz: No address record pkg: https://firmware.netgate.com/pkg/pfSense_factory-v2_3_2_amd64-pfSense_factory-v2_3_2/meta.txz: No address record pkg: https://firmware.netgate.com/pkg/pfSense_factory-v2_3_2_amd64-pfSense_factory-v2_3_2/packagesite.txz: No address record It does that 3 times and then this ERROR: Error trying to get packages list. Aborting... pkg: Repository pfSense-core missing. 'pkg update' required pkg: Unable to open remote repository catalogues. Try running 'pkg update' first. All within a span of less then a minute.  Any thoughts as to why this config works and the other one stalls for a couple hours would be helpful.

Thanks

Okay. Should I file a bug for hiding the Etc zones from pfSense?

Same problem as mine! https://forum.pfsense.org/index.php?topic=118177.0 Some monitors are ok, some not, and it's simply not booting if there are no monitor connected.

This could be caused by any number of dozens of reasons. The information you've given is pretty much the bare bones of what anyone would need to work out the cause. And you haven't said what version of PFS you're installing either (32-bit or 64-bit), or whether your old desktop machine is a 32-bit or 64-bit machine. So I will repeat my previous question and ask if you're booting with the correct version of pfSense for your hardware? If you're trying to install a 64-bit version of software on a 32-bit machine, your installation will hang in just such a way as you describe. Please fully read any questions you get in response to your problem and try to answer them - otherwise you may as well just ignore what's being asked and try sorting things out yourself.

I have the same problem My mbo is Via Epia and i did try to install to ide HDD no way . Different Stick didnt help , on my laptop it goes but i get a different eror . What you can try is go to bios on the hdd you are using ad disable smart and dma set all to manual and hdd typ from auto to LBA. Maybe that will help .

Read over the upgrade guide and the release notes for both 2.2 and 2.3, more likely than not, you need to make some adjust to your captive portal HTML code.

Agreed this is pointless..  Run it on a vm, run it on their little cloudkey, run it in the cloud..  Just no point to messing with the pfsense install to try and get this to run.  If you could get signoff from the developers that this would be fine then ok.. Now that they have really dropped support or suggestion that you run a wifi card in pfsense you can not longer purchase from their store appliances with wifi cards added and they suggest external AP maybe they would think about doing such a thing.. But I wouldn't hold my breath ;) If you want to run multiple things on 1 piece of hardware - then run VM…  I run pfsense on my esxi host, and then I have another vm for my controller, have another for my nas ;)  Which is the other thing people want to run on pfsense..

@Gertjan: I had some spare time yesterday, so I decide to repair my crystal ball. Your question was just great to test it afterwards. This is what I saw : The issue is what your cameras is "seeing". Snort is a "packet inspection system" and the new version that came with 2.3.2 doesn't like what your camera 'sees'. Snort kicks in and filters it out. So : tell snort that your camera is trusted. Can you confirm that my crystal ball is repaired ? Thanks for fixing and dusting off your crystal ball. Yes it seems to be related to SNORT, if its uninstalled prior to upgrade the remote camera continues to stream to my local recorder. I did add a alias of the remote internet IP number and then I added it to snorts "pass list" prior to removal. I did a little "light" reading (too alleviate my noobness) on how to filter logs.  ::) but my "remote" ip never shows up in logs. I reinstalled SNORT and my setting reappeared and my cameras are working still, post upgrade/package reinstall . puzzling. Another way I think of this is, that I am doing a download of a file from a internet server at 2.5mbps all day long to a local computer. If things change I will update. But look like its working.

Hello, If you disable and then re-enable the WAN interface start again to work? Or do you strictly need to reboot?

If it is supported by FreeBSD 10.3 then you should be able to shutdown, install the hardware, power up and it will be available as an interface to assign in Interface->Assign. If it does not appear, then it is not supported, and you won't have broken your existing config.

If the .47 device is a Windows client then it probably has its own firewall settings that respond to ping from the local subnet but not to remote pings from outside the subnet.

For all 64-bit AMD and Intel equipment, use the AMD64 image (the "AMD" is from past history of the evolution of that instruction set - both AMD and Intel make processors that have the "AMD64" architecture/instruction set. USB can be be easily written to a USB stick, and you can boot from that to do the install. Also read: https://doc.pfsense.org/index.php/Installing_pfSense https://doc.pfsense.org/index.php/Writing_Disk_Images

nope! Didn't pay anything for the server at all. Decommissioned at work, so got it for free. I don't think you can disable one CPU in the BIOS, at least I don't see the option. I was told (elsewhere) that the only way is to take it off of the board. If you see the BIOS option, could mind letting me know pls? -San

Make sure you have a default gateway. Check Diag > Routes, make sure you have a "default" line there. If you don't, then go to System > Routing, edit one of the gateways and mark it default, then save/apply and check it again. Try to ping out from the firewall by IP address, see if that works. If you can ping to 8.8.8.8, perhaps set that as a DNS server under System > General Setup and enable forwarding mode in the DNS Resolver. Also you could try disabling DNSSEC.

I tried a fresh install and it doesn't work correctly. I have to do some magic for it to see the hard disks (See https://forum.pfsense.org/index.php?topic=109952.msg613371#msg613371). After it can see the hard disk, it can only see 3 of the 5 NICs I've setup for it. I tried 2.3.3 and it had the same issues.

Still replying to myself… Package pfSense-base was missing. I was sure I had this correct... but no (was it installed to some other slice?) Adding this missing package (pkg install pfSense-base) fixed http://pfap.snet/pkg_mgr_install.php?id=firmware which was previously reporting "Unable to retrieve..." (reference: /etc/inc/pkg-utils.inc get_base_pkg_name()).