Open dkggpeters opened 8 months ago
Network discovery appears to be working now over the last few scans I believe the original problem of not updating was a network issue.
The ARP scan for the main network is tied to interface ix0. I also have 7 vlans attached to the interface ix0 (3 active, 4 no devices currenlty in) which is not being scanned. The networks are identified in my ntopng.conf file. Shouldn't these be included in the ARP scan?
I can confirm this issue exists also in OPNSense with the ntopng plugin 1.3 and ntopng Community v.6.0.240416 rev.0 (FreeBSD 13.2) - Oddly enough, no matter what interface I look at - I get a strange address of 8.0.0.0 which I can't explain - the address range of this interface is 192.168.30.0/24 :
I can confirm this issue exists also in OPNSense with the ntopng plugin 1.3 and ntopng Community v.6.0.240416 rev.0 (FreeBSD 13.2) - Oddly enough, no matter what interface I look at - I get a strange address of 8.0.0.0 which I can't explain - the address range of this interface is 192.168.30.0/24 :
Same here on pfSense in Proxmox, fresh installs, with 3 vlans All interfaces return 8.0.0.0
The problem is due to VLAN tags. If you have an interface named vtnet1.5 you need to activate ntopng on such interface. In fact if you activate instead ntopng on vtnet1 (without .5) packets are sent untagged.
Thanks Luca - but I'm not sure this is the issue. On a bare metal OPNSense running NTopNG I can use discovery - also with VLANs named vlan01.10 and vlan01.20 - just not in a virtualised instance of OPNSense under Proxmox
Environment:
What happened: Network Discovery does not populate devices and only appears to send ARP requests on the Main Lan while ignoring the VLANS. Local networks were setup in the configuration for all Lans.
Debug Information: