#PFSENSE 2.0.3 ISO FULL#
#PFSENSE 2.0.3 ISO PLUS#

Please note: The error occurs in both 2.0.3 RELEASE as well as 21. I guess I could reduce it to 9 seconds with sufficient practice). What would you consider a reasonable interval between a single user toggling a single ruleset, clicking on 'Apply changes' then 'Close' and then clicking on the 'Diagnostics->States->Reset States->Reset' button? (It just took me 13 seconds with a mousepad and clumsy fingers. What do you mean exactly by 'too many filter reloads too fast'?Д®.g. If you trigger too many filter reloads too fast it's possible that check_reload_status is eating the reloadД®vents because they're coming too frequently and it is throttling the reload. I am satisfied that the effect I am seeing is not due to hardware or user error. However, testing within a carefully controlled set of conditions (as described) has been as rigorous and exhaustive as I could make time for. I have only tested on 2.0.3 and the July 4th snapshot of 2.1 RC0.

On a system that is installed to HDD a reboot also flushes the block rule such that it is correctly reinstated. an 'ls' on the /tmp/bug file) result in the block rule being reinstated to the live ruleset, and after a state reset the block rule becomes effective again (a volatile buffer being committed?). the error condition remains.ДЄctions via the console shell that trigger an OS file stat (e.g. I have also tried waiting up to 30 minutes after entering the error state and then accessing various web GUI pages, then resetting states, then stopping the ping, waiting 30min etc. The only remedial action available via the web GUI is to either add another rule or re-save the existing rule. I emphasise that this has nothing to do with resetting states. Several configurations of hardware, routing and rulesets were tried, but for thorough repeated testing I reverted to a completely 'factory default' setup behind an ADSL broadband router with DHCP on WAN/em1, and just 1 user-added firewall rule on the LAN interface. This issue became apparent by chance during initial evaluation of pfSense 2.0.3 RELEASE (i386) 2 weeks ago (as a possible addition to our data-centre hosting setup). The firewall is essentially exhibiting the opposite of the expected, and indicated, behaviour. (possible multiple repeat required here.)ДЄt this point the ICMP echo replies continue, despite the block rule showing as enabled.

start an ICMP echo request (constant ping to remote host on WAN if).

add new ICMP block rule (enabled) LAN->WAN, host->host.

#PFSENSE 2.0.3 ISO FULL#

The error condition can occur after just 1 cycle, but may take 6 full cycles of enabled/disabled/reset-states: Please see the description in my forum post for more details:ДЄ block rule fails completely if toggled between enabled and disabled using the icon to the left of the rule. Release Notes - Target Version (DO NOT EDIT).

#PFSENSE 2.0.3 ISO PLUS#

Release Notes - Plus Target Version (DO NOT EDIT).No Target - New Issues (Base and Packages).No Target - All Open Issues (Base Only).New Issues by Category - No Target+Future.CE-Next - Feedback (Likely needs target changed).

CE-Next - All Closed Issues (Move to specific target).

21.09 Plus - New/Confirmed/In Progress Issues.

21.05.1 Plus Target - All Closed Issues.

Pfsense 2.0.3 iso