Scan Segments Behind a Firewall
Place a daemon for a segment that a firewall separates from the rest of the network, and open the rules it needs.
A segment behind a firewall can be scanned from either side.
| Daemon inside the segment | Daemon outside, scanning through the firewall | |
|---|---|---|
| Segment scanned at | Layer 2 | Layer 3 |
| MAC addresses | Collected | Only from the ARP tables of SNMP devices in the segment |
| Rules through the firewall | Daemon to server only | Daemon to every address in the segment |
| Firewall interference | None | Session helpers on the firewall can answer probes for empty addresses |
See Interfaced and routed subnets for what a routed scan records.
Run the daemon inside the segment
Install the daemon on a host in the segment and create it on the same site as the rest of that location. It scans the segment at Layer 2, and the only traffic crossing the firewall is between the daemon and the server.
| Polling mode | Rule through the firewall |
|---|---|
| DaemonPoll (default) | Daemon → server, TCP 443 for Scanopy Cloud or 60072 for a self-hosted server by default |
| ServerPoll | Server → daemon, TCP 60073 |
Use ServerPoll when the segment allows no outbound connections. Scanopy Cloud rejects ServerPoll URLs on private addresses, so a ServerPoll daemon on a private address needs a self-hosted server on the other side. See Choosing a polling mode.
If the daemon's host has interfaces on both the segment and another network, set Interfaces on the daemon to the interfaces it should scan. See Scanning Isolated Networks from One Host.
Scan through the firewall
Add the segment's subnets to a daemon outside it, as described in Managing Scan Targets. Allow these from the daemon's address into the segment:
| Traffic | Why |
|---|---|
| ICMP echo request and reply | Ping sweep. Hosts that answer ping are recorded without a TCP check |
| TCP to the segment's addresses | Port scan and service probes. A full scan probes all 65,535 ports |
| UDP 161 to switches and routers | SNMP, for interfaces, LLDP and CDP neighbors, and the ARP tables that supply MAC addresses |
| Each integration's port | The port listed in that integration's guide, such as TCP 8006 for Proxmox |
Firewall session helpers and application-layer gateways can complete TCP handshakes for addresses with nothing behind them, which makes empty addresses look like hosts. The scan doesn't record an address on an open port alone, and it warns when addresses on a subnet completed a connection and then answered nothing. To fix it on the firewall, see Phantom Hosts.
Credentials for hosts in the segment
A credential assigned to a host is tried only by a scan that covers that host's subnet. Otherwise the run's Credentials tab shows Credential target outside the scan. Add the host's subnet to the scan of a daemon that can reach it.
Deploy Daemons Across Several Sites
Place daemons for locations joined by a WAN, SD-WAN or VPN, either one per site or scanning remote sites from a central host.
Limit Each Client to Its Own Site
Limit users, API keys and credentials to each client's site, and keep each daemon scanning only its own network.