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

Ok. So that gives me a fresh install with the complete configuration and rrd data restored. Packages are referenced in the configuration but not installed after this, right? In the documentation in https://doc.pfsense.org/index.php/Configuration_Backup_and_Restore it says: 'This page also contains two useful package functions: Reinstall Packages: This button initiates a re-installation of all currently installed packages.' That sounds promising but I can't see this (pfSense Version 2.2.6). Is the documentation outdated or is this feature available starting from pfSense 2.3? If this feature is available: After a fresh install with an old configuration file would I be able to reinstall all packages from here which are referenced in the configuration? -flo-

No worries, in return, a thank you to all involved for the awesome work on the project.

https://forum.pfsense.org/index.php?topic=109513.msg609705#msg609705 an untagged vlan means the client (in your case pfsense) is unaware of it, and shouldn't need any configuration

That's exactly the sort of changes I was expecting! The "pfSense-compact-red.css" theme is not perfect (yet), but is a great example of what is reasonable to accomplish with the new 2.3 structure. Dare I say you're going to need a "Web-GUI-Themes" forum some time soon? (probably jumping the gun…..) Kudos on 2.3, again!

Thanks everyone the issue has been solved.  It was the USB flash drives, possibly in conjunction with the application I was using to make the installer. That YouTube video was an eye opener and I also used rufus. I have always used unetbootin with success plus Kingston USB flash drives.  Not sure why it started failing but now that I have switched to a 4GB verbatim drive I had kicking around and everything works 100%.

@naniam: – Miss the old RRD graphs. The new method works and is interesting but requires a constant changing of parameters to get what I want whereas before I just viewed an area and had everything. The RRD Graphs were one my most used features and gave me quick overview on the installed system. The new way of displaying data is completely unusable, ugly and missing lots of data, that were available before. Please rework this anoying hipster failure.  >:(