From 40438c8ba1f7348d840e807e1c8446f5e8bf5561 Mon Sep 17 00:00:00 2001 From: BBcan177 Date: Tue, 9 Dec 2014 21:56:52 -0500 Subject: XHTML mods All
to
Widget Added alt="" to img tags Closed any open tags > to /> --- config/pfblockerng/pfblockerng_top20.xml | 44 ++++++++++++++++---------------- 1 file changed, 22 insertions(+), 22 deletions(-) (limited to 'config/pfblockerng/pfblockerng_top20.xml') diff --git a/config/pfblockerng/pfblockerng_top20.xml b/config/pfblockerng/pfblockerng_top20.xml index 692917a3..7d2cf033 100644 --- a/config/pfblockerng/pfblockerng_top20.xml +++ b/config/pfblockerng/pfblockerng_top20.xml @@ -134,10 +134,10 @@ info - Top 20 IPv4
Spammer Countries]]> + Top 20 IPv4
Spammer Countries]]> countries4 - + Use CTRL + CLICK to unselect countries]]> select @@ -167,10 +167,10 @@ - Top 20 IPv6
Spammer Countries]]> + Top 20 IPv6
Spammer Countries]]> countries6 - + Use CTRL + CLICK to unselect countries]]> select @@ -201,41 +201,41 @@ List Action - Default : Disabled

- Select the Action for Firewall Rules on lists you have selected.

- 'Disabled' Rules: Disables selection and does nothing to selected Alias.

+ Default : Disabled

+ Select the Action for Firewall Rules on lists you have selected.

+ 'Disabled' Rules: Disables selection and does nothing to selected Alias.

- 'Deny' Rules:
+ 'Deny' Rules:
'Deny' rules create high priority 'block' or 'reject' rules on the stated interfaces. They don't change the 'pass' rules on other - interfaces. Typical uses of 'Deny' rules are:
+ interfaces. Typical uses of 'Deny' rules are:
  • Deny Both - blocks all traffic in both directions, if the source or destination IP is in the block list
  • Deny Inbound/Deny Outbound - blocks all traffic in one direction unless it is part of a session started by traffic sent in the other direction. Does not affect traffic in the other direction.
  • One way 'Deny' rules can be used to selectively block unsolicited incoming (new session) packets in one direction, while still allowing deliberate outgoing sessions to be created in the other direction.
- 'Permit' Rules:
- 'Permit' rules create high priority 'pass' rules on the stated interfaces. They are not the opposite of Deny rules, and don't create - any 'blocking' effect anywhere. They have priority over all Deny rules. Typical uses of 'Permit' rules are:
+ 'Permit' Rules:
+ 'Permit' rules create high priority 'pass' rules on the stated interfaces. They are the opposite of Deny rules, and don't create + any 'blocking' effect anywhere. They have priority over all Deny rules. Typical uses of 'Permit' rules are:
  • To ensure that traffic to/from the listed IPs will always be allowed in the stated directions. They override almost all other Firewall rules on the stated interfaces.
  • To act as a whitelist for Deny rule exceptions, for example if a large IP range or pre-created blocklist blocks a few IPs that should be accessible.
- 'Match' Rules:
+ 'Match' Rules:
'Match' or 'Log' only the traffic on the stated interfaces. This does not Block or Reject. It just Logs the traffic.
  • Match Both - Matches all traffic in both directions, if the source or destination IP is in the list.
    • -
  • Match Inbound/Match Outbound - Matches all traffic in one direction only.
- 'Alias' Rules:
+
  • Match Inbound/Match Outbound - Matches all traffic in one direction only.
    • + 'Alias' Rules:
    'Alias' rules create an alias for the list (and do nothing else). This enables a pfBlockerNG list to be used by name, in any firewall rule or pfSense function, as desired. -
    • Options    - Alias Deny,  Alias Permit,  Alias Match,  Alias Native

      • -
    • 'Alias Deny' can use De-Duplication and Reputation Processes if configured.

      • -
    • 'Alias Permit' and 'Alias Match' will be saved in the Same folder as the other Permit/Match Auto-Rules

      • -
    • 'Alias Native' lists are kept in their Native format without any modifications.
    +
    • Options    - Alias Deny,  Alias Permit,  Alias Match,  Alias Native

      • +
    • 'Alias Deny' can use De-Duplication and Reputation Processes if configured.

      • +
    • 'Alias Permit' and 'Alias Match' will be saved in the Same folder as the other Permit/Match Auto-Rules

      • +
    • 'Alias Native' lists are kept in their Native format without any modifications.
    When using 'Alias' rules, change (pfB_) to ( pfb_ ) in the beginning of rule description and Use the 'Exact' spelling of the Alias (no trailing Whitespace)  Custom 'Alias' rules with 'pfB_ xxx' description will be removed by package if - using Auto Rule Creation.

    Tip: You can create the Auto Rules and remove "auto rule" from the Rule + using Auto Rule Creation.

    Tip: You can create the Auto Rules and remove "auto rule" from the Rule Descriptions, then disable Auto Rules. This method will 'KEEP' these rules from being 'Deleted' which will allow editing for a Custom - Alias Configuration
    ]]> + Alias Configuration
    ]]>     action select @@ -258,7 +258,7 @@ Enable Logging aliaslog - Enable
    + Enable
    Select - Logging to Status: System Logs: FIREWALL ( Log )]]>     select -- cgit v1.2.3