If you run both Pi.Alert and Pi-hole, Pi.Alert will get the information on network devices from Pi-hole. The only way of I know of excluding active devices would be adding their MAC addresses to MAC_IGNORE_LIST in pialert.conf.
this post was submitted on 11 Sep 2023
10 points (85.7% liked)
Selfhosted
37824 readers
474 users here now
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
-
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
-
No spam posting.
-
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
-
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
-
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
-
No trolling.
Resources:
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
founded 1 year ago
MODERATORS
After adding about 20 MAC addresses I gave up and just moved pi.alert to my secondary dns server (a pi zero) which has no docker
Has anyone tried the docker variant of pi.alert? I presume that one must be smart enough to filter out docker ‘devices’
I have it running in a docker container and the subnet setting seems to work. Also should mention it's restricted to eth0.
You can set the subnet to be scanned in the arpnet settings. Restricting the scans to your devices subnet will get rid of all the extra docker IPs.
Yeah i tried setting my subnet to 192.168.3.0/24 (the one used by my intranet) but they still show up