diff options
author | Scott Ullrich <sullrich@pfsense.org> | 2007-04-14 22:23:14 +0000 |
---|---|---|
committer | Scott Ullrich <sullrich@pfsense.org> | 2007-04-14 22:23:14 +0000 |
commit | 0618f66b4337a9dca18d7d3368fcf90589ae5f15 (patch) | |
tree | 781f13ec8503c5a88bd2f57bee945f62e9110555 /usr/local | |
parent | 4cf2b7fd2a624acf8e561ee5378b7c69b913c043 (diff) | |
download | pfsense-0618f66b4337a9dca18d7d3368fcf90589ae5f15.zip pfsense-0618f66b4337a9dca18d7d3368fcf90589ae5f15.tar.gz |
Wrap text in <pre></pre>
Diffstat (limited to 'usr/local')
-rw-r--r-- | usr/local/www/firewall_rules_schedule_logic.php | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/usr/local/www/firewall_rules_schedule_logic.php b/usr/local/www/firewall_rules_schedule_logic.php index 8421852..cab662f 100644 --- a/usr/local/www/firewall_rules_schedule_logic.php +++ b/usr/local/www/firewall_rules_schedule_logic.php @@ -1,7 +1,7 @@ - +<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. 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 |