In this video, I walk through how to self-host NetAlertX, an open-source network discovery and monitoring tool that discovers devices on your network, even some your firewall might miss. Many plugins available to enrich data and you can get alerts when something changes.
Chapters
00:00 Do you know what’s on your network?
01:17 What Is and why use NetalertX
03:18 NetalertX Docker Compose Setup
03:42 Configuring NetalertX Networking
05:58 Running and Scheduling Network Discovery Scans
09:00 NetalertX Plugins
09:38 UniFi Plugin
10:33 Discovered Devices and Monitoring
13:00 Manual and Auto NMAP Scans
14:50 Import Export and Maintenance
In general you can run as many containers as you want with enough resources available.
Do note that running a tool like this and allow it to access multiple networks/vlans it could require additional network configuration which could conflict with your Kasm installation.
I have it deployed via Docker and it’s scanning everything on the current VLAN. I’m trying to get it to scan my other VLANs. I have pfSense and on the VLAN that I wanted scanned, I have this rule:
Screenshot 2025-06-09 at 08-42-42 TheWall.jrfam.net - Firewall Rules LAN
It’s not discovering. I’m not sure if the port is right, that’s the web interface port.
I have the question, trying to discover systems on different VLANs. I checked and found I could ping other systems on different vlans from the nextalertx container but those systems are not discovered by nextalertx.