summaryrefslogtreecommitdiffstats
path: root/usr
diff options
context:
space:
mode:
authorScott Ullrich <sullrich@pfsense.org>2007-04-14 22:28:28 +0000
committerScott Ullrich <sullrich@pfsense.org>2007-04-14 22:28:28 +0000
commite9f661b98c5a61daefcac4520cfaae433b77977b (patch)
treebb44eda03a14c099a8059bc910032459505ea3a2 /usr
parent099ab77e908f2af50cdbba2f997d9c59875557ce (diff)
downloadpfsense-e9f661b98c5a61daefcac4520cfaae433b77977b.zip
pfsense-e9f661b98c5a61daefcac4520cfaae433b77977b.tar.gz
Add some text breaks.
Diffstat (limited to 'usr')
-rw-r--r--usr/local/www/firewall_rules_schedule_logic.php5
1 files changed, 4 insertions, 1 deletions
diff --git a/usr/local/www/firewall_rules_schedule_logic.php b/usr/local/www/firewall_rules_schedule_logic.php
index cab662f..9f714b3 100644
--- a/usr/local/www/firewall_rules_schedule_logic.php
+++ b/usr/local/www/firewall_rules_schedule_logic.php
@@ -1,7 +1,10 @@
<pre>
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.
+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.
</pre> \ No newline at end of file
OpenPOWER on IntegriCloud