LILiK
/
openwrt-packages-dist
5
0
Fork 0
Code Issues 0 Pull Requests 0 Projects 0 Releases 0 Wiki Activity
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
16457 Commits
1 Branch
46 MiB
 
 
 
 
 
 
Tree: a572df4e1b
Branches Tags
${ item.name }
Create branch ${ searchTerm }
from 'a572df4e1b'
${ noResults }
openwrt-packages-dist/net/banip/files/README.md

5.4 KiB
Raw Blame History

banIP - ban incoming and/or outgoing ip adresses via ipsets

Description

IP address blocking is commonly used to protect against brute force attacks, prevent disruptive or unautherized address(es) from access or it can be used to restrict access to or from a particular geographic area — for example.

Main Features

  • support many IP blocklist sources (free for private usage, for commercial use please check their individual licenses):
  • zero-conf like automatic installation & setup, usually no manual changes needed
  • supports four different download utilities: uclient-fetch, wget, curl, aria2c
  • Really fast downloads & list processing as they are handled in parallel as background jobs in a configurable 'Download Queue'
  • full IPv4 and IPv6 support
  • ipsets (one per source) are used to ban a large number of IP addresses
  • supports blocking by ASN numbers
  • supports blocking by iso country codes
  • supports local white & blacklist (IPv4, IPv6 & CIDR notation), located by default in /etc/banip/banip.whitelist and /etc/banip/banip.blacklist
  • auto-add unsuccessful ssh login attempts to 'dropbear' or 'sshd' to local blacklist (see 'ban_autoblacklist' option)
  • auto-add the uplink subnet to local whitelist (see 'ban_autowhitelist' option)
  • per source configuration of SRC (incoming) and DST (outgoing)
  • integrated IPSet-Lookup
  • integrated RIPE-Lookup
  • blocklist source parsing by fast & flexible regex rulesets
  • minimal status & error logging to syslog, enable debug logging to receive more output
  • procd based init system support (start/stop/restart/reload/refresh/status)
  • procd network interface trigger support
  • automatic blocklist backup & restore, they will be used in case of download errors or during startup
  • output comprehensive runtime information via LuCI or via 'status' init command
  • strong LuCI support
  • optional: add new banIP sources on your own

Prerequisites

  • OpenWrt, tested with the stable release series (19.07) and with the latest snapshot
  • a download utility:
    • to support all blocklist sources a full version with ssl support of 'wget', 'uclient-fetch' with one of the 'libustream-*' ssl libraries, 'aria2c' or 'curl' is required

Installation & Usage

  • install 'banip' (opkg install banip)
  • at minimum configure the needed IP blocklist sources, the download utility and enable the banIP service in /etc/config/banip
  • control the banip service manually with /etc/init.d/banip start/stop/restart/reload/refresh/status or use the LuCI frontend

LuCI banIP companion package

  • it's recommended to use the provided LuCI frontend to control all aspects of banIP
  • install 'luci-app-banip' (opkg install luci-app-banip)
  • the application is located in LuCI under 'Services' menu

banIP config options

  • usually the pre-configured banIP setup works quite well and no manual overrides are needed

  • the following options apply to the 'global' config section:

    • ban_enabled => main switch to enable/disable banIP service (bool/default: '0', disabled)
    • ban_automatic => determine the L2/L3 WAN network device automatically (bool/default: '1', enabled)
    • ban_fetchutil => name of the used download utility: 'uclient-fetch', 'wget', 'curl', 'aria2c', 'wget-nossl'. 'busybox' (default: 'uclient-fetch')
    • ban_iface => space separated list of WAN network interface(s)/device(s) used by banIP (default: automatically set by banIP ('ban_automatic'))

  • the following options apply to the 'extra' config section:

    • ban_debug => enable/disable banIP debug output (bool/default: '0', disabled)
    • ban_nice => set the nice level of the banIP process and all sub-processes (int/default: '0', standard priority)
    • ban_triggerdelay => additional trigger delay in seconds before banIP processing begins (int/default: '2')
    • ban_backupdir => target directory for banIP backups (default: '/tmp')
    • ban_sshdaemon => select the SSH daemon for logfile parsing, 'dropbear' or 'sshd' (default: 'dropbear')
    • ban_starttype => select the used start type during boot, 'start' or 'reload' (default: 'start')
    • ban_maxqueue => size of the download queue to handle downloads & IPSet processing in parallel (int/default: '4')
    • ban_fetchparm => special config options for the download utility (default: not set)
    • ban_autoblacklist => store auto-addons temporary in ipset and permanently in local blacklist as well (bool/default: '1', enabled)
    • ban_autowhitelist => store auto-addons temporary in ipset and permanently in local whitelist as well (bool/default: '1', enabled)

Examples

receive banIP runtime information:


/etc/init.d/banip status
::: banIP runtime information
  + status     : enabled
  + version    : 0.2.0
  + fetch_info : /bin/uclient-fetch (libustream-ssl)
  + ipset_info : 11 IPSets with overall 118359 IPs/Prefixes
  + backup_dir : /tmp
  + last_run   : 09.09.2019 16:49:40
  + system     : UBNT-ERX, OpenWrt SNAPSHOT r10962-c19b9f9a26

cronjob for a regular IPSet blocklist update (/etc/crontabs/root):


0 06 * * *    /etc/init.d/banip reload

Support

Please join the banIP discussion in this forum thread or contact me by mail dev@brenken.org

Removal

  • stop all banIP related services with /etc/init.d/banip stop
  • optional: remove the banip package (opkg remove banip)

Have fun!
Dirk