Nothing major would have changed any time recently in that area. Do you know what snapshot you were on before installing the one from the 10th? And have you upgraded again since?

What's the answer to @johnpoz question? also, It's not very polite to post the same question in different parts of the forum. EDIT: or to create multiple threads to get support.

It's in snapshots now and confirmed to be working. So give it a try.

Thanks I think here's a BIG clue in the bios photo. I think some of the cheaper Chinese Celeron 4 port mini pcs have had their BIOSs hacked to disable temperature, because they don't want you to know how hot they can get! I have 2 virtually identical boxes with the same BIOS ID string but totally different bios setups(??).  One is in a plain steel box and gets hot but runs v cool with a small 50mm fan. The second a little more expensive is in an ali case with nice external fins and has the bios temperature readout in the hardware section. I suspect that pfsense.freeBSD is reading the Intel hardware temperature string.  

ACK, makes sense. Everything seems to be working fine but I'll give that a test later. Thanks!

@nmiller0113: Thanks!  I'm curious what it will look like when 2.4 is Stable Release. It will look the same. I just don't recall exactly what happens during the transition from beta to release.

@xpxp2002: @bimmerdriver: @Harvy66: FreeBSD 11.1 will be out soon. I could see them waiting until at least after that. This would allow generation 2 VMs on windows hyper-v 2012R2, which would be a nice cherry on top of 2.4. I got a 2.4 build from a few months ago running on a Gen 2 VM. Been upgrading it ever since with only one issue: the proprietary Hyper-V keyboard driver isn't there so the console can't be used. Might be a dealbreaker for some, but it has worked fine for me for months. I heard this is possible, but I'd prefer to have a working keyboard so I'll stick with generation 1 until generation 2 is properly supported.

Hi. Hoped maybe as this topic was php I had this message today?? Any thoughts, seems a bit odd? - thanks Crash report begins.  Anonymous machine information: amd64 11.0-RELEASE-p10 FreeBSD 11.0-RELEASE-p10 #162 9b57f5336c3(RELENG_2_4): Sun Jul  9 02:29:43 CDT 2017    root@buildbot2.netgate.com:/builder/ce/tmp/obj/builder/ce/tmp/FreeBSD-src/sys/pfSense Crash report details: No PHP errors found. No FreeBSD crash data found.

Don't thank me - than jim P for fixing it, and also adding some nice new features with the ability to add SAN..

Yeah it should be all good now. I accidentally introduced that problem when attempting to address a different bug, but I wasn't 100% done, so I fixed that while I was wrapping up the work I was doing on CSR/Signing and whatnot.

2.4.0-BETA (amd64) built on Wed Jul 05 03:37:29 CDT 2017 FreeBSD 11.0-RELEASE-p10 unbound as a resolver pfblockerNG suricata freeradius 3 Working normal. No problem after update or reboot.

@C0RR0SIVE: I would much prefer the logo to be the same as the one at the main pfSense page, and have the white banner replaced with the same textured image seen on the main page, but instead of it replacing just the banner area, let it cover the entire page… Coloration could be as simple as loading a single image that we choose from in the WebGui at that point and wouldn't be hard to get different colored variants of the texture... [image: 08b67ad5f85b2a437fbe693d3c345275.png] Just throwing ideas out there… But, I do like the idea of being able to place a company logo on the logon screen, that would be more beneficial than a few colors for those that do have multiple instances of pfSense that they need to manage. I agree. The logo and background used for the main site looks very nice. Maybe add some shadowing underneath the username and password field and change the sign in button color to red.

@jimp: I'm not seeing that here on either of mine. What packages, if any, do you have installed on there? And what services are enabled? i tested this on another system and this error comes if the pppoe connection is reset from isp end or they force a disconnection causing pfsense to reconnect pppoe and when that happens this error comes

Package updates != OS Updates. You disabled the OS Update check. Remove the packages widget.

Of course you are right. But I unfortunately just recently invested  :'( my space requirements required a 1U dual net6501-70 solution (Kerberos). I had to find something adequate…

It doesn't matter, it is not a valid question. "Why did my rule that wasn't valid stop working?". It worked before by pure chance, now it doesn't, also by pure chance. DNS is TCP/UDP, period.