That change only affects hitting that issue during booting, as that was the only time we seemed to see it occur. The latest 2.3.1 has a fix for the booting issue, which is what everyone else here was hitting. That appears to be the same root cause, but upon linkup of multiple NICs at exactly the same time. There's a larger architectural issue to be addressed there in the future to fully address the root issue. In the mean time, the message is ugly, but doesn't impact functionality.

Guys Thanks I fixed the issue : Apparently it was the same issue from this Forum : https://forum.pfsense.org/index.php?topic=88467.0 and What I did was go and disable  Disable hardware checksum offload on System>Advanced>Networking on my Pfsense only. Just that. Touched nothing on KVM.

I think i need a solution like on the article: https://mebsd.com/make-build-your-freebsd-word/ifconfig-physical-link-down.html But can i do it without patches?

That page doesn't handle really large state tables well (or at all). No different than it's ever been, would have done same on all previous versions with the same size state table.

Welcome to the wild world of HSTS. HTTP Strict Transport Security https://en.wikipedia.org/wiki/HTTP_Strict_Transport_Security

That one's much different, it's in IPsec. It looks like a known crash there that's confirmed fixed in 2.3. But if you have > 1 vCPU in your VM, you'll want to change it to 1 vCPU until 2.3.1 to avoid hitting this. https://redmine.pfsense.org/issues/6296

Sorry. My mistake (too many nights of little sleep) :-) 2.3-RELEASE (amd64) built on Mon Apr 11 18:10:34 CDT 2016 FreeBSD 10.3-RELEASE

Thanks. Do you still have aes-NI enabled? Looking for anything here….

Thanks for every friend. It's block by isp.I have call isp to unlock it.Thanks a lot.

huh??  You do understand pfsense routes right..  You allow whatever traffic you want to allow between your network segments..  Be it all or none would be up to you..

If it's such a deal, then ok I have pfsense :P Thanks for the advice though! :)

Here is. .png_thumb) .png) .png) .png_thumb) .png) .png_thumb) .png) .png_thumb) .png) .png_thumb) .png) .png_thumb) .png) .png_thumb) .png) .png_thumb) .png) .png_thumb) .png) .png_thumb)

@peske: @jswope - THANK YOU! It helped! Just as info for other users that may experience some problems - in my case the problem was in "Search scope - Level". With "One Level" selected it does not work, but when I've changed it (thanks to jswope) to "Entire Subtree" - everything worked well. Btw, one more question for you jswope: In the page you've referenced a bunch of permissions is assigned to the group, and "WebCfg - All Pages" among others. Isn't this redundant? I've thought that "WebCfg - All Pages" covers everything (default "admin" user has only this permission assigned). Thanks man! You are correct. All Pages is All pages in pfsense GUI

I see there's no reply to this question - giving it a a bump up as the problem doesn't appear to be isolated. I have 1 x ALIX (CF) & 1 x APU4 (SSD). On both since the upgrade to 2.3, I've not been able to duplicate the slice. After an extended wait, the web browser times out and eventually an error log is generated which I've sumbitted for analysis from both units. Crash report begins.  Anonymous machine information: amd64 10.3-RELEASE FreeBSD 10.3-RELEASE #6 05adf0a(RELENG_2_3_0): Mon Apr 11 18:52:07 CDT 2016    root@ce23-amd64-builder:/builder/pfsense-230/tmp/obj/builder/pfsense-230/tmp/FreeBSD-src/sys/pfSense Crash report details: PHP Errors: [10-May-2016 10:46:11 Australia/Sydney] PHP Stack trace: [10-May-2016 10:46:11 Australia/Sydney] PHP  1\. {main}() /usr/local/www/diag_nanobsd.php:0 [10-May-2016 10:46:11 Australia/Sydney] PHP  2\. nanobsd_clone_slice() /usr/local/www/diag_nanobsd.php:102 [10-May-2016 10:46:11 Australia/Sydney] PHP  3\. nanobsd_update_fstab() /etc/inc/pfsense-utils.inc:2282 [10-May-2016 10:46:11 Australia/Sydney] PHP  4\. mkdir() /etc/inc/pfsense-utils.inc:2294

Yep, it solved the problem. Thank you!

If you use "whitelist" instead of "allow" on the ACL entry for your custom target category that should stop it from processing the others.

Thank virgilio, I had not noticed the option to customize the graph, it helps me. I'm hoping if anyone has any other option to manage my custom scripts, as the filer does.

I would submit a feature request on redmine. https://redmine.pfsense.org/