Copyright (C) 2011 Marcello Coutinho All rights reserved. */ /* ========================================================================== */ /* Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: 1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. 2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. THIS SOFTWARE IS PROVIDED ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. */ /* ========================================================================== */ ]]> Describe your package here Describe your package requirements here Currently there are no FAQ items provided. pfblockerlists 1.0 /usr/local/pkg/pfblocker.inc pfBlocker

Firewall

pfblocker_lists.xml General /pkg_edit.php?xml=pfblocker.xml&id=0 Lists /pkg.php?xml=pfblocker_lists.xml Top Spammers /pkg_edit.php?xml=pfblocker_topspammers.xml&id=0 Africa /pkg_edit.php?xml=pfblocker_Africa.xml&id=0 Asia /pkg_edit.php?xml=pfblocker_Asia.xml&id=0 Europe /pkg_edit.php?xml=pfblocker_Europe.xml&id=0 North America /pkg_edit.php?xml=pfblocker_NorthAmerica.xml&id=0 Oceania /pkg_edit.php?xml=pfblocker_Oceania.xml&id=0 South America /pkg_edit.php?xml=pfblocker_SouthAmerica.xml&id=0 XMLRPC Sync /pkg_edit.php?xml=pfblocker_sync.xml&id=0 Alias aliasname Description description Action action Update Frequency cron Network ranges / CIDR lists listtopic Alias Name aliasname Example: Badguys
Do not include pfBlocker name, it's done by package.
International, special or space characters will be ignored in firewall alias names.
]]> input 20 List Description description input 90 none 'URL or local file' - Add direct link to list (Example: Ads, Spyware, Proxies )

Note:
Compressed lists must be in gz format.
Downloaded or local file must have only one network per line and could follows PeerBlock syntax or this below:
Network ranges: 172.16.1.0-172.16.1.255
IP Address: 172.16.1.10
CIDR: 172.16.1.0/24 ]]> rowhelper Format format select gzgz txttxt URL or localfile url input 75 List Action Deny Inbound
Select action for network on lists you have selected.

'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 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:

• 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.

'Alias' and 'Disabled' Rules:

• 'Alias' rules create an alias for the list (and do nothing else). This enables a Pfblocker list to be used by name, in any firewall rule or Pfsense function, as desired.
• 'Disabled' rules are kept for future use, but nothing is done with them.

While creating rules with this list, keep aliasname in the beginning of rule description and do not end description with 'rule'. Custom rules with 'Aliasname something rule' description will be removed by package.]]> action select Deny InboundDeny_Inbound Deny OutboundDeny_Outbound Deny BothDeny_Both Permit InboundPermit_Inbound Permit OutboundPermit_Outbound Permit BothPermit_Both Alias onlyAlias_only DisabledDisabled Update frequency cron Never
Select how often List files will be downloaded]]> select NeverNever Every Hour01hour Every 4 Hours04hours Every 12 Hours12hours Once a dayEveryDay Custom list listtopic CIDR custom Example: 192.168.1.0/24]]> textarea 50 10 base64 pfblocker_php_install_command(); pfblocker_php_deinstall_command(); pfblocker_validate_input($_POST, &$input_errors); sync_package_pfblocker();