diff options
| author | Scott Ullrich <sullrich@pfsense.org> | 2007-04-14 22:28:22 +0000 |
|---|---|---|
| committer | Scott Ullrich <sullrich@pfsense.org> | 2007-04-14 22:28:22 +0000 |
| commit | 1fa1ddc7af9c3e137d9d0ee04576bd984337c359 (patch) | |
| tree | c26b16cbe33e9a0d0c38e1d5739c0f6ab708d0ab /usr/local/www/firewall_rules_schedule_logic.php | |
| parent | 49decb6638e24eec20f9fbaf2ba655d69575489d (diff) | |
| download | pfsense-1fa1ddc7af9c3e137d9d0ee04576bd984337c359.zip pfsense-1fa1ddc7af9c3e137d9d0ee04576bd984337c359.tar.gz | |
Add some text breaks.
Diffstat (limited to 'usr/local/www/firewall_rules_schedule_logic.php')
| -rw-r--r-- | usr/local/www/firewall_rules_schedule_logic.php | 5 |
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 |
