Differences

This shows you the differences between two versions of the page.

--- computing:piholeonblack [2023/02/27 01:10] – oemb1905
+++ computing:piholeonblack [2026/10/24 14:26] (current) – oemb1905
@@ Line 10: / Line 10: @@
 -------------------------------------------
+Update: I no longer use Beaglebone blacks for the piholes as they became too slow around Trixie. I've retained this tutorial, however, both to document pihole setup generally and/or in case I eventually get a newer Beaglebone to tinker with. At present, I use virtualized piholes.
 This tutorial is for setting up a vanilla pihole instance on the Beagle Bone Black using a stripped down/clean Debian OS.  The first step is to update/upgrade, then remove the files in /opt/ which are not required, and lastly to remove the software that will conflict with the pihole software and that is installed by default by BBB.  (Do not remove anything starting with bb- as that is firmware needed for the device to work properly - believe me, I have tried.)  Save removal of connman for after pihole installation takes over DNS.  Here is what I do in order:
@@ Line 50: / Line 52: @@
 {{ :computing:openwrt.png?direct&600 |}}
-Replace 6, 192.168.11.20 with your pihole's LAN address.  In my case, I instruct my router to issue a static local ip to the device (which pihole also recommends).  Once you complete this last step, restart the router.  Then, restart all of the clients on the LAN.  Lastly, to verify that the pihole DNS is in fact being used, use the admin GUI in your browser and navigate to Tools / Network, and ensure each device came back online using the pihole DNS.  Please note: Beagle Bone users specifically, will see an entry pihole device itself listed as not using the pihole's own DNS in red - this is because connman was not using the pihole DNS for one of the stages above.  You will see another more current entry for the pihole device itself indicating that it is now utilizing its own DNS.
+Replace 6, 192.168.11.20 with your pihole's LAN address.  In my case, I instruct my router to issue a static local ip to the device (which pihole also recommends).  Once you complete this last step, restart the router.  Then, restart all of the clients on the LAN.
+. To stop the pihole from cutting off internet from clients:
+  sudo nano /etc/dnsmasq.d/02-custom-settings.conf
+  dns-forward-max=5096
+  min-cache-ttl=300
+  rebind-domain-ok=
+To stop some sanity checking and annoying load reports, etc., do the following:
+  nano /etc/pihole/pihole-FTL.conf
+  PRIVACYLEVEL=0
+  RATE_LIMIT=10000/60
+  CHECK_LOAD=false
+  MAXDBDAYS=7
+The new locations are in ''nano /etc/pihole/pihole.toml'' and search for:
-Thanks to [[https://frdmtoplay.com/running-pi-hole-on-the-beagle-bone-black/|Freedom to Play]], [[https://bacnh.com/how-to-setup-pi-hole-with-openwrt/|Embedded Knowledge]], and Jared from [[https://gitlab.com/ABQLUG|ABQ GLUG]] for the idea to tinker with this.
+  count = 10000
+  interval = 60
+  privacylevel = 0
+  load = false
+  maxDBdays = 91
- --- //[[jonathan@haacksnetworking.com|oemb1905]] 2021/10/27 11:17//
+ --- //[[alerts@haacksnetworking.org|oemb1905]] 2025/08/31 02:59//

Haack's Wiki

User Tools

Site Tools

Differences

Page Tools