Pi.Alert picking up Docker networks and containers hosted on same server

Submitted ⁨⁨1⁩ ⁨year⁩ ago⁩ by ⁨giddy@aussie.zone⁩ to ⁨selfhosted@lemmy.world⁩

Hi all,

I have Pi.Alert (along with Pi.hole) running on a RPi4. I recently moved my Dokuwiki instance (running in Docker) onto the same device and now Pi.Alert is complaining about lots of new devices. If I look at the IP addresses I can see they correspond to the network interfaces created by Docker. Is there any way to exclude these networks from Pi.Alert?

Thanks

source

Comments

Sort:hotnew top

giddy@aussie.zone ⁨1⁩ ⁨year⁩ ago
Has anyone tried the docker variant of pi.alert? I presume that one must be smart enough to filter out docker ‘devices’

source
- darcmage@lemm.ee ⁨1⁩ ⁨year⁩ ago
  I have it running in a docker container and the subnet setting seems to work. Also should mention it’s restricted to eth0.
  
  source
boerbiet@feddit.nl ⁨1⁩ ⁨year⁩ ago
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.

source
- giddy@aussie.zone ⁨1⁩ ⁨year⁩ ago
  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
  
  source
darcmage@lemm.ee ⁨1⁩ ⁨year⁩ ago
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.

source
- giddy@aussie.zone ⁨1⁩ ⁨year⁩ ago
  Yeah i tried setting my subnet to 192.168.3.0/24 (the one used by my intranet) but they still show up
  
  source