![]() ![]() Perhaps the Netgate guys can respond to those. ![]() Yeah, these are all core to pfSense PHP itself and not related to Suricata. They were different BUT weere about missing firewall rules or such. They were different BUT weere about missing firewall rules or said in 6100 SLOW in comparison to Protectli is one I saved.Īlso had 100's of messages I receive via Pushover. PHP Fatal error: Uncaught Error: Call to undefined function isURL() in /etc/inc/pfsense-utils.inc:2724Īlso had 100's of messages I receive via Pushover. Thrown in /etc/inc/pfsense-utils.inc on line 2724 ![]() PHP Fatal error: Uncaught Error: Call to undefined function isURL() in /etc/inc/pfsense-utils.inc:2724 But deployment of the fix in pfSense will likely wait until AFTER the current 23.01-RC goes to production release because the Netgate team wishes to minimize changes in that branch while completing RC is one I saved.Īnd I got no internet connection on the LAN. I will roll the fix (if it proves out) into the 6.x Suricata used on pfSense. If everything pans out, the fix will be applied to Suricata upstream in the upcoming 6.0.11 release (no release date established yet) and in Suricata "master" which is currently the 7.0-RC branch. Some further testing of the proposed fix is happening. The bug particularly adversely impacts Suricata when using Inline IPS Mode and runmode=workers. ![]() Short story is that both OPNsense and pfSense are subject to this bug, and the bug is most likely to present itself in heavy traffic scenarios (speed tests on Gigabit links definitely being one of those). Details can be found in the following Suricata Redmine tickets: There has been some movement on the potential cause of the stall/hang bug with netmap and Suricata. Just to close the loop here on this issue: ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |