Problem with dashboard and docker crashing

[TheCableGuy99]

Hi,

I started looking into this last night as I want to monitor multiple vLANs.

I first tried a docker image but it keeps crashing for some unknown reason (tried it twice).

So I installed it on a Debian 11 VM. The problem with this is that it's nowere near as nice as the Docker version which has dark mode and a control panel and extra field columns.

I really want the dark mode and control panel interface and can't understand why the two appear to be different versions.... can anyone help?

Also I'm not using PiHole if that makes any difference?

Thanks.

[jokob-sk]

I assume you are using my fork. Please check this message if you issues with the latest image: https://github.com/jokob-sk/Pi.Alert/issues/163

[leiweibau]

Just as there is an evolved fork of Pi.Alert version as a Docker image, there is also an evolved fork as a standalone version (https://github.com/leiweibau/Pi.Alert). I hope my hint does not bother @jokob-sk

[TheCableGuy99]

Thanks guys, so how do I compare which to use?

I was also having trouble getting it to scan multiple vLANs but i'm not sure if that was a limitation of it being in a docker?

I don't mind running it as a VM instead of in a docker container but I need the following features in order:

It's stable
Scans multiple vLANs
Additional features like the control panel/admin area.

Thanks again guys.

[jokob-sk]

All good @leiweibau ;) we support each-other here.

I'm in the midle of releasing a bigger feature piece so that might still take a while as I want to make it relatively stable (also being pretty pressed with real-life issues these days, such as regular work), but the image mentioned in this post seems to be pretty stable:

https://github.com/jokob-sk/Pi.Alert/issues/163#issuecomment-1416509878

jokobsk/pi.alert_dev:sha-b5f0a64

You can follow this advice on setting up multiple vlans:
https://github.com/jokob-sk/Pi.Alert/blob/main/docs/SUBNETS.md

PS. Please read carefully the settings descriptions, I try to be pretty specific describing those, but the feature list being this long and the app that configurable, you need to read it pretty carefully. With great power comes great responsibility...or something

[TheCableGuy99]

Thanks, i'm just installing a VM now to try leiweibau's version first as I'm thinking docker has a limitation which is stopping me scanning multiple vLANs. I was running it on my Synology NAS so I wonder if that's anything to do with it also. If it doesn't work i'll give yours a try.

[jokob-sk]

As mentioned, multiple vlans can be configured in docker by following this doc: https://github.com/jokob-sk/Pi.Alert/blob/main/docs/SUBNETS.md

Quote from the above documentation:

on the SCAN_SUBNETS setting.
...

• Append e.g.: -vlan=107 to the interface field (e.g.: eth0 -vlan=107) for multiple vlans. More details in this issue

[TheCableGuy99]

Well i've got your docker version installed and it's more stable since I turned off "API". I've added the subnet and it's only scanning some of them....

SCAN_SUBNETS=['192.168.1.0/24 --interface=ovs_bond0','192.168.5.0/24 --vlan=5 --interface=ovs_bond0','192.168.10.0/24 --vlan=10 --interface=ovs_bond0','192.168.15.0/24 --vlan=15 --interface=ovs_bond0','192.168.20.0/24 --vlan=20 --interface=ovs_bond0','192.168.25.0/24 --vlan=25 --interface=ovs_bond0','192.168.30.0/24 --vlan=30 --interface=ovs_bond0','192.168.35.0/24 --vlan=35 --interface=ovs_bond0','192.168.50.0/24 --vlan=50 --interface=ovs_bond0','192.168.200.0/24 --vlan=200 --interface=ovs_bond0']

It's returning devices on vlan1,20 and 50 but nothing on any other vlan is showing. One vLAN with plenty of devices is vLAN10 which is the IoT devices.

Any ideas?

[jokob-sk]

Glad there is progress. Can you please open an issue on my fork so everything is in the right place also for the others to see?

…

On Thu, 9 Mar 2023, 12:59 TheCableGuy99, ***@***.***> wrote: Well i've got your docker version installed and it's more stable since I turned off "API". I've added the subnet and it's only scanning some of them.... SCAN_SUBNETS=['192.168.1.0/24 --interface=ovs_bond0','192.168.5.0/24 --vlan=5 --interface=ovs_bond0','192.168.10.0/24 --vlan=10 --interface=ovs_bond0','192.168.15.0/24 --vlan=15 --interface=ovs_bond0',' 192.168.20.0/24 --vlan=20 --interface=ovs_bond0','192.168.25.0/24 --vlan=25 --interface=ovs_bond0','192.168.30.0/24 --vlan=30 --interface=ovs_bond0','192.168.35.0/24 --vlan=35 --interface=ovs_bond0',' 192.168.50.0/24 --vlan=50 --interface=ovs_bond0','192.168.200.0/24 --vlan=200 --interface=ovs_bond0'] It's returning devices on vlan1,20 and 50 but nothing on any other vlan is showing. One vLAN with plenty of devices is vLAN10 which is the IoT devices. Any ideas? — Reply to this email directly, view it on GitHub <#219 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AW5URDGAYG2IR4NNMCCQP4DW3E2PLANCNFSM6AAAAAAVTURKAU> . You are receiving this because you were mentioned.Message ID: <pucherot/Pi .***@***.***>

[TheCableGuy99]

Done, thanks.