summaryrefslogtreecommitdiffstats
path: root/usr/local/www/firewall_rules_schedule_logic.php
diff options
context:
space:
mode:
authorScott Ullrich <sullrich@pfsense.org>2007-04-14 22:08:42 +0000
committerScott Ullrich <sullrich@pfsense.org>2007-04-14 22:08:42 +0000
commit4cf2b7fd2a624acf8e561ee5378b7c69b913c043 (patch)
tree32cac7c51d6a9373eb0b4d88da2dc95a9cb210fe /usr/local/www/firewall_rules_schedule_logic.php
parent92f86ca6682e8916873b67299908dd7461e17c93 (diff)
downloadpfsense-4cf2b7fd2a624acf8e561ee5378b7c69b913c043.zip
pfsense-4cf2b7fd2a624acf8e561ee5378b7c69b913c043.tar.gz
Add a note about firewall rule schedule logic that will pop up in a new window describing how pass rules work when they are outside of the schedule window, etc.
Diffstat (limited to 'usr/local/www/firewall_rules_schedule_logic.php')
-rw-r--r--usr/local/www/firewall_rules_schedule_logic.php7
1 files changed, 7 insertions, 0 deletions
diff --git a/usr/local/www/firewall_rules_schedule_logic.php b/usr/local/www/firewall_rules_schedule_logic.php
new file mode 100644
index 0000000..8421852
--- /dev/null
+++ b/usr/local/www/firewall_rules_schedule_logic.php
@@ -0,0 +1,7 @@
+
+When working with pfSense based schedules, the logic is a bit different from the normal pfSense rules.
+
+For example, the rules are evaluated from top to bottom. If you have a pass rule and the rule is outside of the schedule, the traffic will be BLOCKED regardless of pass rules that occur after this rule.
+
+In these cases you will want to change the pass rule to a block style rule to get the needed functionality.
+
OpenPOWER on IntegriCloud