- name: pihole-by-rajannpatel
- description: strictly confined snap packaging of the Pi-hole DNS sinkhole open source project
- snapcraft: snap-pi-hole/snap/snapcraft.yaml at main · rajannpatel/snap-pi-hole · GitHub
- upstream: GitHub - pi-hole/pi-hole: A black hole for Internet advertisements · GitHub
- upstream-relation: contributor to upstream open source project
- interfaces:
- : network-observe
- request-type: this interface should be auto-connectes upon install, the user has to manually connect it today for basic software functionality
- reasoning:
- : network-observe
This interface is needed for client MAC & Vendor Discovery (for the Network Table in the pi-hole web UI)
Pi-hole FTL continuously monitors the local network’s ARP cache (by reading /proc/net/arp and using Netlink sockets) to map client IP addresses to their hardware MAC addresses and vendors.
Without network-observe FTL cannot access this mapping, meaning the Network tab in the Pi-hole Admin Console will not fully populate, and you won’t be able to group or identify clients by MAC address.
network-observe is also useful for diagnostic port and socket verification
Diagnostic tools included in the snap (like pihole status, pihole.check-system, and pihole.snapdebug) query socket states (by scanning /proc/net/tcp and /proc/net/udp) to verify whether port 53 (DNS) or port 80/8123 (HTTP) are correctly bound and listening.
Without network-observe these check commands will trigger AppArmor denials when attempting to verify port statuses.
