IT Solutions Technology Blog

root@rpi-iot-jsho-pihole:~# pihole -up
[✓] Supported OS detected
[✓] Update local cache of available packages
[✓] Building dependency package pihole-meta.deb
[✓] Installing Pi-hole dependency package

[i] Checking for updates…
[i] Pi-hole Core: up to date
fatal: unable to access ‚https://github.com/pi-hole/web.git/‘: Could not resolve host: github.com

Error: Unable to update local repository. Contact Pi-hole Support.

root@rpi-iot-jsho-pihole:~# curl -sSL https://install.pi-hole.net | PIHOLE_SKIP_OS_CHECK=true bash

[✓] Root user check

.;;,.
.ccccc:,.
:cccclll:. ..,,
:ccccclll. ;ooodc
‚ccll:;ll .oooodc
.;cll.;;looo:.
.. ‚,‘.
.‘,,,,,,‘.
.‘,,,,,,,,,,.
.‘,,,,,,,,,,,,….
….“‘,,,,,,,’…….
……… …. ………
………. ……….
………. ……….
……… …. ………
……..,,,,,,,’……
….‘,,,,,,,,,,,,.
.‘,,,,,,,,,‘.
.‘,,,,,,‘.
..“‘.

[i] SELinux not detected
[✓] Update local cache of available packages

[✓] Checking apt-get for upgraded packages… up to date!

[✓] Building dependency package pihole-meta.deb
[✓] Installing Pi-hole dependency package

[i] PIHOLE_SKIP_OS_CHECK env variable set to true – installer will continue
[✓] Check for existing repository in /etc/.pihole
[i] Update repo in /etc/.pihole…HEAD is now at 0f7803b Pi-hole Core v6.0.6 (#6118)
[✓] Update repo in /etc/.pihole

[✓] Check for existing repository in /var/www/html/admin
[i] Update repo in /var/www/html/admin…HEAD is now at 1eaddca Pi-hole Web v6.1 (#3354)
[✓] Update repo in /var/www/html/admin

[✓] Checking for user ‚pihole‘

[i] FTL Checks…

[✓] Detected ARMv6 architecture
[i] Latest FTL binary already installed (v6.1), verifying integrity…
[i] Local binary up-to-date. No need to download!
[✓] Installing scripts from /etc/.pihole

[i] Installing configs from /etc/.pihole…

[✓] Installing latest Cron script

[i] Installing latest logrotate script…
[i] Existing logrotate file found. No changes made.
[✓] man pages installed and database updated
[i] Testing if systemd-resolved is enabled
[i] Systemd-resolved is not enabled
[i] Restarting services…
[✓] Enabling pihole-FTL service to start on reboot…
[✓] Restarting pihole-FTL service…
[✓] Deleting existing list cache
[✗] DNS resolution is currently unavailable
[✓] DNS resolution is available
[i] Neutrino emissions detected…

[✓] Preparing new gravity database
[✓] Creating new gravity databases
[✓] Pulling blocklist source list into range
[i] Using libz compression

[i] Target: https://raw.githubusercontent.com/StevenBlack/hosts/master/hosts
[✓] Status: No changes detected
[✓] Parsed 143685 exact domains and 0 ABP-style domains (blocking, ignored 0 non-domain entries)

[✓] Building tree
[i] Number of gravity domains: 143685 (143685 unique domains)
[i] Number of exact denied domains: 0
[i] Number of regex denied filters: 0
[i] Number of exact allowed domains: 0
[i] Number of regex allowed filters: 0
[✓] Optimizing database
[✓] Swapping databases
[✓] The old database remains available
[✓] Cleaning up stray matter

[✓] Done.

[i] The install log is located at: /etc/pihole/install.log
[✓] Update complete!

Core version is v6.0.6 (Latest: v6.0.6)
Web version is v6.1 (Latest: v6.1)
FTL version is v6.1 (Latest: v6.1)

root@rpi-iot-jsho-pihole:~#

root@rpi-iot-jsho-arpwatch:~# apt-get install ssmtp mailutils

root@rpi-iot-jsho-arpwatch:~# vi /etc/ssmtp/ssmtp.conf
#
# Config file for sSMTP sendmail
#
# The person who gets all mail for userids < 1000
# Make this empty to disable rewriting.

root=josef.schuster@dpsolution.de

# The place where the mail goes. The actual machine name is required no
# MX records are consulted. Commonly mailhosts are named mail.domain.com

mailhub=smtp.ionos.de:587

# Where will the mail seem to come from?

rewriteDomain=dpsolution.de

# The full hostname

hostname=rpi-iot-jsho-arpwatch

# Use SSL/TLS before starting negotiation

UseTLS=Yes
UseSTARTTLS=Yes

AuthUser=josef.schuster@dpsolution.de
AuthPass=<password>
AuthMethod=LOGIN

# Are users allowed to set their own From: address?
# YES – Allow the user to specify their own From: address
# NO – Use the system generated From: address

FromLineOverride=YES

root@rpi-iot-jsho-arpwatch:~# vi /etc/ssmtp/revaliases
#
# sSMTP aliases
#
# Format: local_account:outgoing_address:mailhub
#
# Example: root:your_login@your.domain:mailhub.your.domain[:port]
# where [:port] is an optional port number that defaults to 25.

root:josef.schuster@dpsolution.de:smtp.ionos.de:587
arpwatch:josef.schuster@dpsolution.de:smtp.ionos.de:587

root@rpi-iot-jsho-arpwatch:~# chfn -f ‚root at myhost‘ root

root@rpi-iot-jsho-arpwatch:~# echo -e ‚Subject: test\n\nTesting ssmtp‘ | sendmail -v josef.schuster@dpsolution.de
[<-] 220 kundenserver.de (mreue107) Nemesis ESMTP Service ready
[->] EHLO rpi-iot-jsho-arpwatch
[<-] 250 STARTTLS
[->] STARTTLS
[<-] 220 OK
[->] EHLO rpi-iot-jsho-arpwatch
[<-] 250 SIZE 141557760
[->] AUTH LOGIN
[<-] 235 Authentication succeeded
[->] MAIL FROM:<josef.schuster@dpsolution.de>
[<-] 250 Requested mail action okay, completed
[->] RCPT TO:<josef.schuster@dpsolution.de>
[<-] 250 OK
[->] DATA
[<-] 354 Start mail input; end with <CRLF>.<CRLF>
[->] Received: by rpi-iot-jsho-arpwatch (sSMTP sendmail emulation); Sun, 20 Apr 2025 19:37:11 +0200
[->] From: „root at myhost“ <josef.schuster@dpsolution.de>
[->] Date: Sun, 20 Apr 2025 19:37:11 +0200
[->] Subject: test
[->]
[->] Testing ssmtp
[->] .
[<-] 250 Requested mail action okay, completed: id=1Mqal4-1ut2W73fk0-00noa4
[->] QUIT
[<-] 221 kundenserver.de Service closing transmission channel

root@rpi-iot-jsho-arpwatch:~#

root@rpi-iot-jsho-arpwatch:~# apt-get install arpwatch

root@rpi-iot-jsho-arpwatch:~# chfn -f ‚arpwatch at myhost‘ arpwatch

root@rpi-iot-jsho-arpwatch:~# vi /etc/arpwatch/arpwatch.conf
eth0 -a -n 192.168.1.0/24 -m josef.schuster@dpsolution.de

root@rpi-iot-jsho-arpwatch:~# systemctl enable arpwatch@eth0

root@rpi-iot-jsho-arpwatch:~# systemctl start arpwatch@eth0

root@rpi-iot-jsho-arpwatch:~# systemctl status arpwatch@eth0
● arpwatch@eth0.service – arpwatch service on interface eth0
Loaded: loaded (/lib/systemd/system/arpwatch@.service; enabled; preset: enabled)
Active: active (running) since Sun 2025-04-20 17:45:36 CEST; 2h 25min ago
Docs: man:arpwatch(8)
Process: 400 ExecStartPre=/usr/bin/touch -a eth0.dat (code=exited, status=0/SUCCESS)
Process: 434 ExecStartPre=/bin/chown $RUNAS eth0.dat (code=exited, status=0/SUCCESS)
Process: 436 ExecStart=/usr/sbin/arpwatch -u $RUNAS -i eth0 -f eth0.dat $ARGS $IFACE_ARGS -F ${PCAP_FILTER} (code=exited, status=0/>
Main PID: 437 (arpwatch)
Tasks: 1 (limit: 395)
CPU: 2.022s
CGroup: /system.slice/system-arpwatch.slice/arpwatch@eth0.service
└─437 /usr/sbin/arpwatch -u arpwatch -i eth0 -f eth0.dat -N -p -F

Apr 20 17:45:33 rpi-iot-jsho-arpwatch systemd[1]: Starting arpwatch@eth0.service – arpwatch service on interface eth0…
Apr 20 17:45:36 rpi-iot-jsho-arpwatch arpwatch[437]: Running as uid=106 gid=111
Apr 20 17:45:36 rpi-iot-jsho-arpwatch arpwatch[437]: listening on eth0
Apr 20 17:45:36 rpi-iot-jsho-arpwatch systemd[1]: Started arpwatch@eth0.service – arpwatch service on interface eth0.

root@rpi-iot-jsho-arpwatch:~#

Pi-hole ‚conditional forwarding‘ – if not configured as your DHCP server so Pi-hole typically won’t be able to determine the names of devices on your local network as a result tables such as Top Clients will only show IP addresses