Closed s33d1ing closed 1 year ago
Hi there!
Thanks for the detailed description.
Have you tried to add the vlan parameter to your subnets as described here?
https://github.com/jokob-sk/Pi.Alert/blob/main/docs/SUBNETS.md#support-for-vlans
I can't test this but users reported that this approach has helped them.
Thanks, j
I messed around with this a bit more and tried the vlan parameter but didn't have any luck. I ended up joining the pi to a wireless network on the 192.168.0.0 subnet as well as the wired 172.27.0.0 network. I updated the config to use the other interface for those subnets:
SCAN_SUBNETS=['172.27.10.0/24 --interface=eth0','172.27.20.0/24 --interface=eth0','172.27.30.0/24 --interface=eth0','192.168.86.0/24 --interface=wlan0','192.168.96.0/24 --interface=wlan0']
I have a Ubiquiti Dream Machine Pro with multiple networks (VLANs) set up but they are not isolated (i.e. devices on separate VLANs can ping each other). I set up Pi.Alert using a Host network on my Pi with IP address 172.27.10.30. The Pi can ping and nmap scan devices on 172.27.0.0 and 192.168.0.0 however Pi.Alert can only detect devices on 172.27.0.0, not on 192.168.0.0. I tried adding "--vlan" to the end of the 192.168.0.0 subnets in the SCAN_SUBNETS property but it made no difference. Does anyone have any insight?
Paste last few lines from
pialert.log
Paste your
pialert.conf
(remove personal info)Paste your
docker-compose.yml
and.env
(remove personal info)docker-compose.yml
.env
Screenshots If applicable, add screenshots to help explain your problem.