This is solved.  This was my fault due to old wiring. Switch was plugged into the old router not the main switch.

Thanks! I will try this out during weekend  8)

Last time, I changed to another USB memory stick (larger one), flash the NanoBSD to the new stick, export config from old one, boot up with the new one, then in the new one I chose "import" and all good!

picture3  

https://doc.pfsense.org/index.php/Writing_Disk_Images

@adam65535: If you do decide to downgrade that member make sure you use a backup from the previous version and not 2.3.  I am pretty sure you can't use a 2.3 config on previous 2.2 and 2.1 versions. I have a full backup and an config backup from the previous version . I allways make backups before any update . The ideea behind 2.3 is ok but my opinion is that it was a to early relase and it's unstable and has a big lack of features and packages that existed before 2.3.

sforsythe: I replied back on your ticket but wanted to reply here as well to make sure you see it. adam65535's theory sounds plausible. The fact that turning off the secondary makes the problem stop indicates a problem along the lines of an IP conflict, which is what the scenario he describes ends up being. It's something similar along those lines.

check the sticky. https://forum.pfsense.org/index.php?topic=109690.0

Oh thanks for your help.  Thought that was the case but wasn't sure.  Looks like there were a few APUs we had out there that must have been running SSDs and some others that were running nano off an SD card like you said.  So that's where I got confused and because it's been so long since I worked on those I just lost track of it.  The perils of aging!! Thanks  ;)

I could have swore that in the past week, the download link (USB Memstick Installer Image) at https://portal.pfsense.org had a LOT of older versions, going way back. Maybe I'm remembering another link?

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.