One of the reasons for the 2.3 upgrade was to simplify the package install and maintenance abilities. The flip side is that existing packages need to be updated to meet the new criteria and some of the original maintainers aren't around. If the package you're looking for hasn't been upgraded to 2.3, you'll have to reinstall it manually.

Yes searching is easy, just type some words like "haproxy 2.3 error" produces exactly 10 results for me, several having more or less the same information about removing old files. Or if you search for "haproxy 2.3" the very first result is a "Installation and Upgrades / HEADS UP on 2.3 upgrade if using haproxy". Anyway if your still having issues after trying the removal of old files, please do post the error messages you experience and maybe some advice specific to your installation can be provided. Regards, PiBa-NL

@Colin: I had a similar issue due to my default gateway not being set during the upgrade process. Same here. Did you find a workaround?

Eh, never mind, hardware died so it's a moot point now. At least I have regular config backups.

What Phil said. Specifically, something that was communicating with the web GUI's web server. Likely normal and safe to disregard.

Your gateway monitor delay depends on what your monitor IP is configured as. Where you're seeing 1-2 ms response times, it's either something at the same physical location as you that you're monitoring, or you have a fiber connection. Anything coax or copper, you're going to have 10+ ms to your next hop router past where it touches the coax or copper. Nothing about that looks high at all, all very much normal.

@ScottyDM: I do not have spare machines to test new updates on. And at this point my budget is extremely limited. Just about everybody has spare machines to test on.  They just don't realize it. Oracle VirtualBox addresses both of the issues you cite; spare machines and budget.  Run as many as you like, and they are free.

Alright, I had to open up a support ticket to get a resolution to this problem.  A couple things I wanted to share in case someone else stumbles upon this post with the same problems: I had to move my installation to a spare computer, the 7541 never worked for me as installation hardware. The support guy said that they've seen issues with the / drive being larger than 4GB so he had me resize that and add the rest of the drive capacity to /usr. Serial output is disabled in the standard kernel and I had to use the embedded kernel. Netgate's old documentation stated that LAN was port 5 and WAN was port 6…. after a fresh install with embedded kernel and the ability to console again we found that not to be true. These 4 adjustments finally made it work and I'm back up and running.  Hopefully this will help somebody else in the future.

What output is before that? It could be sending output to a different console (if you're watching the video console, it might be going to the serial console)

When you say it's failing to boot, is hyperv failing to find a boot device or is pfsense (freebsd) failing to find a device to mount? If it's the 2nd one, take a look at this post, it sorted my problems. https://forum.pfsense.org/index.php?topic=109802.msg612250#msg612250

Just edit the OpenVPN server instance and set the topology to net30, and you'll be back to where you were pre-upgrade.

An example of how to remove references to old packages: https://forum.pfsense.org/index.php?topic=110096.msg613137#msg613137

@jimp: There are already a couple threads for this, but it is one we intend to bring back pretty soon once the post-release fervor dies down and we have the time. Very good. Please ensure whomever is working on the nut package tests the nut dashboard widget thoroughly and adds it to the package.  I noticed a bug when adding and saving the widget in my 2.2x NanoBSD installs on a Soekris 6501 box.

It was under the packages section of the release notes: https://doc.pfsense.org/index.php/2.3_Removed_Packages My gosh… the list of package removed is sooooo long... Better stay in 2.2.6 ......

Regarding crashes, in 2.3-RELEASE (i386) I see frequent crash reports due to errors on physical Internet links (i.e. ISP errors)regardless of site, platform (physical or virtual machine) and method of installation (upgrade from 2.2.2 or 2.2.6). The crashes are true. I'm not sure if this is relevant, we use IPsec, but not HA IPsec/Dynamic DNS.

It's not broken. Search through the forums, been discussed 1000x.

Thanks, I think I get the gist of what you said. Speak of the devil, tinkertry did start talking about the new web interface: https://tinkertry.com/vsphere-html5-web-client-update-1-dot-2-arrives