Pihole / Raspberry Pi Documentation

Secondary server — a Raspberry Pi that supports the main ../homelab/README in various ways.

Quick Reference

Property	Value
Hostname	`raspi`
LAN IP	`192.168.2.112`
Tailscale IP	`100.89.172.56`
Connection to Dockhand	Hawser agent (env=2)
Docker Files	`/home/artanis/` (Desktop + TS_KH_Bridge dirs)

Hardware

Property	Value
Model	Raspberry Pi 4 Model B Rev 1.2
CPU	Cortex-A72 (ARM v8), 4 cores
RAM	1.8 GB total (~963 MB used at idle)
Swap	199 MB
OS	Debian GNU/Linux 12 (Bookworm)
Kernel	6.12.47+rpt-rpi-v8 (aarch64)
Storage	32 GB microSD (`/dev/mmcblk0`) — 19 GB used

Pi-hole

Pi-hole runs natively on the Pi OS (not in Docker). It serves as the DNS server for the entire LAN — all clients including Gluetun on the homelab point to 192.168.2.112 for DNS.

Property	Value
Core	v6.3
Web Interface	v6.4
FTL	v6.4.1
Status	Blocking enabled, listening on port 53 (UDP+TCP, IPv4+IPv6)

Updates available: Core → v6.4, Web → v6.4.1, FTL → v6.5. Run sudo pihole -up to update.

Stacks

Stack	Status	Purpose
stacks/home_assistant	Running	Home automation
stacks/ts_kh_bridge	Stopped	Tailscale inter-tailnet bridge
stacks/portainer_agent	Running	Portainer remote agent

How It Supports the Homelab

Home Assistant — Home automation hub; runs on the Pi for low-power always-on operation and USB device access (Zigbee/Z-Wave stick on /dev/ttyUSB0)
Tailscale Bridge — Bridges two separate Tailnets together (Home ↔ KH) — currently stopped
Portainer Agent — Allows a Portainer instance (elsewhere) to manage this Pi's Docker remotely

Key Differences from Homelab

No centralized DockerFiles directory — compose files are scattered across ~/Desktop/ and ~/TS_KH_Bridge/
Home Assistant uses network_mode: host (full host network) for mDNS/Bluetooth/Zigbee discovery
Much lighter workload — only 3 stacks, 5 containers total
Pi-hole — Network-wide DNS ad-blocker running natively on the Pi OS. All LAN clients use 192.168.2.112 as their DNS server

2.2 KiB Raw Blame History