Don't know what to tell you. Before the upgrade, staff access to our webpage worked, after, it did not. When I checked the  "Enable NAT Reflection for 1:1 NAT", staff access was restored. I didn't touch anything except the upgrade button.

Trying to upgrade a Netgate C2758 from 2.2 to 2.2.3 still says there's a digital image invalid error.  This is from the repo at https://firmware.netgate.com/auto-update/full_install/amd64 I presume.  As others have reported, disabling image sig checking doesn't help, either. Only workaround for me is to download it, the upload it back manually while ignoring the image check error. Just tried this 5 minutes ago and it's still complaining…

Welcome on board; you will find here a great community in the true FreeBSD spirit, with some (many) extremely talented people (me excluded, as I have claimed myself the title of eternal noob on this forum)  ;D People are nice over here, and always willing to help out. What often helps of course is if you provide clear questions, and clear information as to what you've done yourself, what errors you've seen, etcetera. I think I sort of missed your question to begin with; what is it you need help with? Can you formulate concrete, detailed, questions? As a suggestion: given church, I would setup a VLAN for your guests, and put some content filtering on it (Squid + Squidguard, or Dansguardian). So keep LAN for trusted computers, and VLAN for guests. Captive Portal seems typical for this setup too. On the firewall level, I would absolutely add BB's pfBlockerNG, a package you can't do without. Snort, or Suricata, comes to mind too of course (layered defense: pfBlockerNG blocks bad IP's based on reputation lists, Snort/Suricata examine content of packages and block when something bad is found). Depending on how many guests you will have on your network you will probably also like some traffic shaping, but although I have that in my setup, I have a limited number of clients in my networks which makes it easy to configure. You probably have many, and I am not sure how you could set this up efficiently, so perhaps people more knowledgeable in this area (remember, eternal noob is my on this forum ;D ) can help you there.

Hmm, no issues with Snort on my setup after updating to 2.2.3… but reinstall usually fixes issues.

Get a bigger card, really. Failing that, avoid installing any packages whatsoever.

Affected workstations were rebooted to try to resolve this but failed to get addresses.  Only after another pfSense reboot, and subsequent workstation reboots were they able to get addresses.  Everything is working great now

Also confirming - All done through "auto-updater". Two Soekris 6501-50's on i386 v2.2.2 nanobsd to v2.2.3 upgraded successfully, with package reinstall all OK.  :) Two Soekris 6501-50's on i386 v2.1.5 nanobsd to v2.2.3 upgraded successfully, with package reinstall all OK.  :) Thanks for this update!

@jimp: For what it's worth, I have PPPoE at home and upgraded yesterday while testing the release and there were no problems here. It linked back up immediately after boot. +1. IMO this is the old regressed HW specific issue that's been there ever since 2.2 and ever before 2.1.5.

Thanks for the response! The first few times, other packages such as snort were downloading ok, but not the OpenVPN Client export utility.  Now it just installed correctly on both of my machines.  Maybe it just took a while to sync a mirror?  Either way, all is well now.  This is resolved. Sincerely, kkm

Just upgraded from 2.2.2 to 2.2.3. It took maybe 5 minutes.  8) Everything is running good from what I see. I upgraded it remotely.. logged in via OpenVPN and saw there was an update, ran the auto-updater with full backup and it rebooted. I reconnected with OpenVPN and everything is back as normal. Hardware: Jetway NF9HG Motherboard 8GB Kingston HyperX DDR3-1600 1.35v 128GB SanDisk x110 mSATA SSD OpenVPN export package BandwidthD package

OK, this worked, sort of. Not sure if the configuration is bonkers or if the system threw a hissy-fit because it's configured for a fixed IP that won't work here… ...need to create a pseudo Internet gateway for it first and upload a 2.2.3 system from there. Anyway, one way or the other I'll get it done ;) Thanks!

it installed to mSATA drive, ada0. that must me the correct destination as this isn't the "nanobsd platform". its listed as "pfsense". anyways, its up and running

Why don't you just do a full install on the HDD? On nanobsd, entire slice is rewritten on upgrades and switched to on reboot, totally unsuitable for similar "tweaks". (Beyond that, the size of /var and /tmp ramdisks is configurable, provided sufficient RAM size of course…)