This is my personal configuration, including:
- WALLY3K'S big blocklist collection - I'm using the non-crossed list
- Whitelist - originally taken from here with a few addition of my own.
I'm running pi-hole on a Raspberry Pi 3 Model B+ and a Mikrotik hAP ac, setting pi-hole as the upstream DNS provider for the Mikrotik.
I've setup the pihole_conf.sh script to be running every hour as a cronjob.
This is just a personal preference, it's way easier for me rather than setup some redundant bootstrapping tool, thus involve manual steps.
I'm also assuming that all permissions (i.e. to /var/log) already setup the way you like to.
- Clone the repo, assuming to
/opt/pihole_config:git clone https://github.com/amitizle/pihole_config.git opt/pihole_config. - Setup the cronjob (using
crontab -e):0 */1 * * * bash -c "cd /opt/pihole_config && git pull && ./pihole_conf.sh &>> /var/log/pihole_config.log"
Here's a list of some environment variables you can setup in order to customize your experience using this script. All variables have got sane defaults so no need to change those usually.
| Variable name | Description |
|---|---|
FIREBOG_LIST_TYPE |
There are three types in Wally3k's list: tick, nocross and all. |
WHITELIST_FILE |
The full path to the whitelist input file |
DRY_RUN |
Set to 1 to do everything but running the pihole commands (i.e pihole -w and pihole -g) |
PIHOLE_BIN |
A full path to the bin file pihole to run command with (i.e pihole -w and pihole -g) |
ADLIST_LIST_DEST |
The destination file to write the adlist.list file to (change it for testing) |
NOTE: The Whitelist file is parsed at the moment with the following rules:
- Every line starts with
#is treated as a comment.- Empty lines are ignored.
- Every line can only contain one domain.