Describe your package hereDescribe your package requirements hereCurrently there are no FAQ items provided.pfblockerngtopspammers1.0pfBlockerNG: Top 20 Spammer Countries/usr/local/pkg/pfblockerng/pfblockerng.incpfBlockerNG: Save Top20 settingsGeneral/pkg_edit.php?xml=pfblockerng.xml&id=0Update/pfblockerng/pfblockerng_update.phpAlerts/pfblockerng/pfblockerng_alerts.phpReputation/pkg_edit.php?xml=/pfblockerng/pfblockerng_reputation.xml&id=0IPv4/pkg.php?xml=/pfblockerng/pfblockerng_v4lists.xml&id=0IPv6/pkg.php?xml=/pfblockerng/pfblockerng_v6lists.xml&id=0Top 20/pkg_edit.php?xml=/pfblockerng/pfblockerng_top20.xml&id=0Africa/pkg_edit.php?xml=/pfblockerng/pfblockerng_Africa.xml&id=0Asia/pkg_edit.php?xml=/pfblockerng/pfblockerng_Asia.xml&id=0Europe/pkg_edit.php?xml=/pfblockerng/pfblockerng_Europe.xml&id=0N.A./pkg_edit.php?xml=/pfblockerng/pfblockerng_NorthAmerica.xml&id=0Oceania/pkg_edit.php?xml=/pfblockerng/pfblockerng_Oceania.xml&id=0S.A./pkg_edit.php?xml=/pfblockerng/pfblockerng_SouthAmerica.xml&id=0P.S./pkg_edit.php?xml=/pfblockerng/pfblockerng_ProxyandSatellite.xml&id=0Logs/pfblockerng/pfblockerng_log.phpSync/pkg_edit.php?xml=/pfblockerng/pfblockerng_sync.xml&id=0listtopicLINKSFirewall Alias
Firewall RulesFirewall Logs]]>
infocountries4
Top 20 Spammer Countries
Use CTRL + CLICK to unselect countries
]]>
IPv4 Countries]]>select20begincountries6
IPv6 Countries
]]>select20endList ActionDefault: 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 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:
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 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' 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: '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.
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
Descriptions, then disable Auto Rules. This method will 'KEEP' these rules from being 'Deleted' which will allow editing for a Custom
Alias Configuration ]]>
actionselectEnable LoggingaliaslogEnable
Select - Logging to Status: System Logs: FIREWALL ( Log )]]>
selectAdvanced Inbound Firewall Rule SettingslisttopicinfoNote: In general Auto-Rules are created as follows:
Inbound - 'any' port, 'any' protocol and 'any' destination
Outbound - 'any' port, 'any' protocol and 'any' destination address in the lists
Configuring the Adv. Inbound Rule settings, will allow for more customization of the Inbound Auto-Rules. Select the pfSense 'Port' and/or 'Destination' Alias below:]]>
autoportsEnable Custom PortcheckboxaliasportsbeginDefine AliasaliasportsClick Here to add/edit Aliases
Do not manually enter port numbers. Do not use 'pfB_' in the Port Alias name.]]>
21aliasesportendautodestEnable Custom Destinationcheckboxaliasdest,autonotbeginaliasdestClick Here to add/edit Aliases
Do not manually enter Addresses(es). Do not use 'pfB_' in the 'IP Network Type' Alias name.]]>
21aliasesnetworkInvertautonotInvert - Option to invert the sense of the match.
ie - Not (!) Destination Address(es)]]>
checkboxendCustom ProtocolautoprotoDefault: any Select the Protocol used for Inbound Firewall Rule(s).]]>select4Click to SAVE Settings and/or Rule Edits. Changes are Applied via CRON or
'Force Update']]>listtopic
pfblockerng_php_install_command();
pfblockerng_php_deinstall_command();
pfblockerng_validate_input($_POST, $input_errors);
global $pfb;
$pfb['save'] = TRUE;
sync_package_pfblockerng();