Thanks guys! This is fixed and will be in 2.3.2: https://github.com/pfsense/FreeBSD-ports/commit/4c3d8e6bdef27b5c601954b63f8a165247f77425

@chpalmer: Thanks for that link Paint!  I did look around but didn't run into that earlier. I was able to put hands on today and we changed the WAN interface on this particular box from the gigabit  (em) port to the 10/100 (fxp) port which seems to have fixed the issue. Now that Im back home Im kicking myself for not trying out one of the other gigabit ports to see if they all did it.  Ill get help from the owner and try that as well if I can pin him down and get him to move the wire. I want to continue to diagnose and will do a packet capture later this weekend or Monday after I get some sleep. My pleasure.  Everything working?

Nope - it's OK, sorry for the scare … completely on me. My apologies! It's due to this issue ... https://forum.pfsense.org/index.php?topic=114345.0. I never would have guessed that a shellcmd (that doesn't exit) would block a bunch of services, but it does. That was a surprise finding. Struggling to try to run a command at startup (even in the background). Again, sorry!

It probably isn't the best naming convention in the world, but it's short for "control of MAC address". I'd be fine with renaming all those "MAC Address" if you want to submit a PR.

Hehe oops I was thinking you were describing 'Associated Panels Show/Hide' in General Setup for some reason.

Hi! No, this is totally different. My DHCP WAN never recovers while pppoe does and and sets correct route.

That's something in the VM subsystem. The time of the dump was Tue Jun 28 08:03:43 2016 (in the system's configured timezone), and appears to be on the kernel from prior to the upgrade. Was that about the time it rebooted post-upgrade? The closest semi-related crash I can find is this. https://lists.freebsd.org/pipermail/freebsd-bugs/2012-July/049368.html It's not the same as that, but does appear it might be md-related in your case. You using /var as a RAM disk? It something that's repeatable if you reboot the system, or upgrade again?