Thanks your further help and fast response. Followed your instructions to apply the patch.  Got the error "Patch can NOT be applied cleanly", which I noted, then continued. The patch works, the checkbox "Disable automatic dashboard auto-update check" does now stop WAN activity on dashboard page refresh, and can be toggled,  which then results in  WAN activity and I assume  allows the auto update to take place. I've only done brief testing and not checked for anything else affected, however it looks like the fix is OK here. J.

+1 for Rufus, works with every single ISO I've used it to put on a USB drive and boot/install from. Clonezilla, centos, xenserver, windows 7, etc etc. Dead simple to use to, just choose iso file and click go

That fix was merged, it'll be in 2.3.1.

Nope.  Something wasn't updated to change the installation screen back to the dashboard.

Just performed the updated.. OSPF still working great. Thanks for the effort jimp!

@cmb: Are all of you seeing it using pfblocker's DNSBL? That's the issue here. https://redmine.pfsense.org/issues/6116 Not for mine. Read that over and it seems unrelated. No firmware upgrade or update. Just a reboot will stop the logging. The icon shows as running and the ps output confirms that too. Another thing is when I mentioned earlier that I tested if logging was working before I Restarted Unbound the package manager did in fact refresh and checked for updates. It seems to me the logging is just not kicking in. The more I look into Unbound the less I think it is with it "NOT" running, but just an issue with the logs. If the package manager had not been able to show progress in the refresh I might have thought it was a problem with Unbound not running. I am using DNSBL but never saw any issue in the upgrade logs during beta to release 2.3. Nothing in the pfblockerng logs going  back a month also. I may only need to do a clean install.  If yea does not chime in here, we may be kicking a dead horse. I will redo to a clean install in the next day or so and update back here. FYI. Full install with HDD, not nano or SSD.

you could set it up all virtual, with virtual network cards & virtual clients. this can be done on any laptop/desktop that is less then 8yrs old. pfSense config(=1 file) can be downloaded from diagnostics–>backup/restore

@phil.davis: …possibly even a checkmark that says you have read them before proceeding with the update It could even ask a few questions about the content of the release notes and only let you upgrade if you get the answers right.  :-\ Why not?  We are a dealer that sells a product in which we have to do this very kind of thing if we want to keep selling the latest and greatest.

Graphs in email are gone: https://forum.pfsense.org/index.php?topic=110179.0 Not sure if or when they might be possible again.

The command that runs``` /usr/local/bin/wol

The function is still there and works as always. Ensure a CARP VIP is selected on the main page of the Quagga settings of both units.

having same issues after ugprade. after fresh 2.3 install and config restore. i'm going back to 2.2.4 https://forum.pfsense.org/index.php?topic=110047.0

@ewhac: While we're about it, what does it take to pfSense-ify a FreeBSD package, making it suitable for v2.3?  upsmon/nut has gone missing, and I'm rather keen on getting it working again. See the sticky threads on the packages board. Lots of info about that there. At the OS level, the binary packages are the same (they just come from our pkg server), but it needs a new meta port to include the pfSense-specific files and any php files need converted to use bootstrap. NUT is one we intend to bring back ASAP, but we're still pretty busy with the post-release influx of issues/support.

I've also solved it, with me it was an improperly configured WAN connection.

My guess would be an incompatible cipher suite. Android 4.1.2 is pretty much ancient. A lot has happened in SSL/TLS in the last four years. Probably time to upgrade. This might help: http://blog.dev-area.net/2015/08/13/android-4-1-enable-tls-1-1-and-tls-1-2/