Simple yet complex

[brucepleat]

Some complexities on my home network that may be problematic:
Unifi UDR-SE with multiple VLANs.
The main network is a /23 (running ~300 devices, lots of IoT!). The other VLANs are /24 or /28.
One Proxmox VE server. It has one Trixie VM. It is running Portainer Stacks. Most Docker containers are running off Portainer Stacks (though Portainer itself and a few others are docker compose). Total of anywhere from six to twenty Stacks and forty to seventy containers (depending on various projects).
Perhaps 15-20 of the containers (and more ports) are through "gluetun" VPN. In its docker config, I set FIREWALL_OUTBOUND_SUBNETS: "(CIDR)/16" to "whitelist" all of the UDR-SE networks and more (I'm being lazy with the "/16"). Because it seems to only support one range, I can't also add the Docker 172 ranges.

Apparently each Stack (docker compose file) apparently creates its own virtual network?

When Scanopy runs (on a container in that setup, self-hosted), a few things I noticed:

1. Stops at 100 hosts. Asks me to "Upgrade". Click that, go to (https://scanopy.net/pricing), which says Community edition is for up to 100 hosts - but then at the bottom, it says "If you prefer to self-host, the Community plan is free with no host limits". Is the limit 100 or unlimited for self-hosting?

2. My main network (main subnet) is a /23. For whatever reason, Scanopy keep adding a /24 - even when I delete it, it reappears a short time later. Thoughts on this?

3. It should be seeing the other services on the same host but it's not. (I know other tools do - Dashy+DashySync and Dozzle both access /var/run/docker.sock:/var/run/docker.sock:ro without issues. Is this due to Can't access server after first install (docker compose / dockge) #1?

Look forward to hearing back... :)

[mayanayza]

Hello! For item 1, v0.15.2 lifts the 100-host limit in favor of unlimited hosts. You'll need to do a DB reset, but after that you won't see that message any more.

For item 2, the daemon periodically checks networks that it's interfaced with and re-creates them on the server; this is needed for scanning so that host <> subnet interfaces can be established. In terms of why it's coming back as a /24 instead of a /23 - I'll need to dig a bit more and will get back to you.

For item 3, what does your compose look like and what does the daemon log on startup + when a discovery session is initiated? Both should have banner sections that summarize config relevant to startup/discovery respectively that'll help troubleshoot further.