Skip to content
This repository has been archived by the owner on Dec 14, 2020. It is now read-only.

Ipset script installation instructions

Jump to bottom
Jack Yaz edited this page May 14, 2017 · 87 revisions

NOTE: This page is helpful instructions on installing the various maintained scripts if there are any issues please turn to the respective thread for support by the author.

ATTENTION: Make sure that you have a backup of your JFFS partition in case something goes wrong. If your using multiple scripts from this make sure they dont run all at the same time that will decrease performance, use sleep command to make the script run at separate times or use && to make them run after each other.

Table of Contents

Search IPset lists for an IP

When using the scripts from this page, there is a chance that a site/IP address you regularly access ends up being blocked. Depending on how many scripts you are using, it can be time consuming to try and determine which ipset list is causing the block.

The below steps will show you how to add a command you can run that will search all of the ipset lists in use, irrespective of their script source, for a provided IP.

Follow the general script installation instructions:

  • Enable and format JFFS through WEB UI first (if not already enabled)

  • Install entware (if not already installed)

  • Install the coreutils-paste package

opkg install coreutils-paste

  • Using your favourite text editor (e.g. nano), add the below into /jffs/configs/profile.add

  • Please make sure you only add the function that applies to the version of ipset that your router supports.

  • For ipset-v4:

MatchIP() { # Check IP against ipset lists
  if [ -z "$1" ]; then
    echo "Specify IP to check through ipset lists. Exiting."
  else
    GREEN='\033[0;32m'
    RED='\033[0;31m'
    NC='\033[0m' # No Color
    for TestList in $( (iptables -L -t raw && iptables -L) | grep " set" | tr -s ' ' | cut -d' ' -f7 | paste -s); do
      ipset -q --test $TestList $1 && echo -e "$1 found in ${GREEN}${TestList}${NC}" || echo -e "$1 not found in ${RED}${TestList}${NC}"
    done
  fi
}
  • For ipset v6:
MatchIP() { # Check IP against ipset lists
  if [ -z "$1" ]; then
    echo "Specify IP to check through ipset lists. Exiting."
  else
    GREEN='\033[0;32m'
    RED='\033[0;31m'
    NC='\033[0m' # No Color
    for TestList in $( (iptables -L -t raw && iptables -L) | grep "match-set" | tr -s ' ' | cut -d' ' -f7 | paste -s); do
      ipset -q test $TestList $1 && echo -e "$1 found in ${GREEN}${TestList}${NC}" || echo -e "$1 not found in ${RED}${TestList}${NC}"
    done
  fi
}

  • Restart your SSH session to pull in the profile change

  • Use the command as below

MatchIP 8.8.8.8

# Sample output
8.8.8.8 not found in YAMalwareBlock1IP
8.8.8.8 not found in YAMalwareBlock2IP
8.8.8.8 not found in YAMalwareBlockCIDR
8.8.8.8 not found in WhitelistDomains
8.8.8.8 not found in BlacklistDomains
8.8.8.8 not found in I-BlocklistTheOnionRouterCIDR
8.8.8.8 not found in I-BlocklistTheOnionRouterSingle
8.8.8.8 not found in BluetackDshieldCIDR
8.8.8.8 not found in BluetackDshieldSingle
8.8.8.8 not found in BluetackSpiderCIDR
8.8.8.8 not found in BluetackSpiderSingle

Tor and Countries Block

This example shows how to block incoming connection from Tor nodes (iphash set type — number of ip addresses) and how to block incoming connection from whole countries (nethash set type - number of ip subnets).

  • Enable and format JFFS through WEB UI first (if not already enabled)

  • Then place this content to /jffs/scripts/create-ipset-lists.sh

  • Then make it executable:

chmod +x /jffs/scripts/create-ipset-lists.sh
  • Finally call this at the end of your existing /jffs/scripts/services-start or /jffs/scripts/post-mount:
# Load ipset filter rules
sh /jffs/scripts/create-ipset-lists.sh

You may also run /jffs/scripts/create-ipset-lists.sh from command line or reboot router to apply new blocking rules immediately. Note that if you change the script country list or any other part, it would need a router reboot to take effect: There are checks to prevent it from reloading the sets if the sets are already existing.

You can create a handy alias in your profile (in /opt/etc/profile or /jffs/configs/profile.add)

If you have ipset v4:

alias blockstats='iptables -L -v | sed "2q;d"; iptables -L -v | grep " set"'

If you have ipset v6:

alias blockstats='iptables -L -v | sed "2q;d"; iptables -L -v | grep "match-set"; ip6tables -L -v | grep "match-set"'

If you have ipset v6 + latest version of scripts that use the raw table:

alias blockstats='iptables -t raw -L -v | sed "2q;d"; iptables -t raw -L -v | grep "match-set"; ip6tables -L -v | grep "match-set"'

Then you can just issue 'blockstats' from the command prompt to see how well your blocklists are doing (see blocked packet count and byte count)

Note that every time you do something on the web UI or through your android app or ios app to control your router that affects reloading the firewall rules, /jffs/scripts/firewall-start will be called, so the iptables rules that are defined outside will be wiped out. To reinstate the rules as defined by this script, you'd need to add this to your existing /jffs/scripts/firewall-start:

# Reinstate the ipset rules if they have been created already
[ "$(uname -m)" = "mips" ] && MATCH_SET='--set' || MATCH_SET='--match-set'
for ipSet in $(ipset -L | sed -n '/^Name:/s/^.* //p'); do
  case $ipSet in
    AcceptList) iptables-save | grep -q "$ipSet" || iptables -I INPUT -m set $MATCH_SET $ipSet src -j ACCEPT;;
    TorNodes|BlockedCountries|CustomBlock) iptables-save | grep -q "$ipSet" || iptables -I INPUT -m set $MATCH_SET $ipSet src -j DROP;;
    MicrosoftSpyServers) iptables-save | grep -q "$ipSet" || iptables -I FORWARD -m set $MATCH_SET $ipSet dst -j DROP;;
    *) iptables-save | grep -q "$ipSet" || iptables -I FORWARD -m set $MATCH_SET $ipSet src,dst -j DROP;;
  esac
done

For support on this script please visit this forum thread on SnBForums

iblocklist-loader

Description: This is a multi-purpose blocking script, and can be a replacement for the old Peerguardian Scripts.

In addition, this script can also be used to block hackers, spiders, bogon ips, various organisations and ISPs, etc. This also blocks Tor and proxies as well. The full list of what it can block is available on the iblocklist site. You can see the free lists on that site and their descriptions (by clicking on the list name).

The script uses the zipped IP range data from the iblocklist site and creates single ip sets and CIDR sets from that for ipset 6.x and uses iptreemap for ipset 4.x It also has both WhitelistDomains and BlacklistDomains functionality to explicitly handle any domains that you'd want to allow or block.

Follow the general script installation instructions:

  • Enable and format JFFS through WEB UI first (if not already enabled)

  • Then place this content to /jffs/scripts/iblocklist-loader.sh

After you decide what sources you'd like to block, these are the steps to use the script: Identify the lists in the script in the top section and note the indexes (the number after the word List) You can than add your chosen indexes in the line that reads BLOCKLIST_INDEXES=

  • Then make it executable:
chmod +x /jffs/scripts/iblocklist-loader.sh
  • Finally call this at the end of your existing /jffs/scripts/services-start or /jffs/scripts/post-mount:
# Load ipset filter rules
sh /jffs/scripts/iblocklist-loader.sh

There are other settings on the script that is documented within the script itself that should be self explanatory. If you have questions or need further details, please ask on the forum thread on SnBForums.

Dynamically Ban Malicious IP's

Description: N/A

NOTE: If you define a USB disk location for the $DIR variable in my IPSET_Block.sh script, it will allow the script to restore the Banned list of IPs rather than create an empty Blacklist IPSET each time you reboot.

  • Enable and format JFFS through WEB UI first (if not already enabled)

  • Then place the content to /jffs/scripts/IPSET_Block.sh

  • Then make it executable:

chmod +x /jffs/scripts/IPSET_Block.sh
  • Finally call this at the end of your existing /jffs/scripts/services-start or /jffs/scripts/post-mount:
# Load ipset filter rules
sh /jffs/scripts/IPSET_Block.sh init nolog
  • then append the following line to /jffs/scripts/services-start:
cru a IPSET_SAVE   "0 * * * * /jffs/scripts/IPSET_Block.sh save"    #Every hour
cru a IPSET_BACKUP "0 5 * * * /jffs/scripts/IPSET_Block.sh backup"  #05:00 every day
  • This will make this script run on a schedule it will run every at 00:00 , to verify that the entry works after its added just type:
cru l
Clone this wiki locally