Network Control & Transparency

StacksAtlas provides granular control over which network environment it monitors. Whether you are using a multi-homed workstation or a virtualized server, you can precisely define the "Listening" environment.

The Global Adapter Selector

Located in the top application header, the Adapter Selector is the primary way to manage your physical scanning interface.

Active Interface Display

The header displays the currently active interface in a high-visibility badge:
  • IP Address: The local address assigned to the interface.
  • CIDR Notation: The automatically calculated network range based on the subnet mask (e.g., /24).
  • Discovery Range: The actual start and end IPs the engine is currently sweeping.

Switching Adapters

  1. Click the active interface badge to open the selection menu.
  2. The menu lists all physical network adapters detected by the system.
  3. Status Awareness: The system displays the operational status (Up/Down) for each adapter to help troubleshoot missing connections.
  4. Select a new adapter.
  5. Instant Switch: StacksAtlas immediately terminates active sweeps on the old interface and re-initializes on the new one. No restart is required.

Network Range Transparency

Understanding where the engine is scanning is critical for network security.
  • Real-time Logic: As soon as an adapter is selected, the backend calculates the valid scanning range.
  • Gateway Awareness: The engine identifies the local gateway to ensure it understands the perimeter of the local segment.

Multi-NIC, VLANs & the Interfaces tab (Business)

On appliances with multiple adapters (Ethernet, Wi-Fi, Tailscale, Docker host NIC), use Settings → Interfaces to govern how each NIC is used.

Adapter roles

Assign one or more roles per interface (see Settings → INTERFACES):
RolePurpose
DefaultGeneral-purpose adapter; baseline binding when no specialized role applies.
Hub SyncPreferred path for federation traffic (useful when Tailscale or a dedicated uplink is enabled).
Alerts / SIEMOutbound alert and syslog traffic when SIEM export is enabled on the Infrastructure tab.
Discovery FallbackNIC used when a scan scope is set to Auto-Detect on the SCANNING tab.
Tunnel adapters (e.g. Tailscale) are excluded from discovery pickers by default but can be assigned Hub Sync for remote federation.
For HTTP/HTTPS ports, syslog targets, and API tokens, see Infrastructure settings.

VLAN scope labels

When you add subnets in Settings → SCANNING (network scopes), you can tag VLAN or location labels. See the full Scan settings guide for CIDR binding, protocol toggles, and engine tuning. Fleet CSV exports and the device grid show site, location, and reporting node columns for multi-site inventories.
On a Central Hub, scan policy and per-node interface policies can be pushed from Settings → SCANNING and the Hub fleet dashboard so remote sites adopt consistent configuration.

Header vs Interfaces tab

The header adapter selector switches the active discovery NIC for quick single-subnet work. The Interfaces tab is the durable policy store for multi-homed and fleet deployments.

Remote Power Management

Managing the power state of network assets is often required for maintenance or energy savings.

Wake-on-LAN (WoL)

StacksAtlas supports sending "Magic Packets" to remotely boot offline workstations and servers.
  • Requirements: The target device must have WoL enabled in its BIOS/UEFI and network adapter settings, and a known MAC in inventory.
  • Execution: From any Device Drawer, if a device is offline, a "Wake Device" button will appear. The packet leaves on the active discovery adapter (same L2 broadcast domain).
  • Confirmation: After sending the packet, StacksAtlas will prioritize polling that device to confirm successful boot-up.
  • Limitation: Classic WoL does not cross routers. Remote or routed sites need directed broadcast / helper support on the network gear, or wake from a Node on that LAN.
StacksAtlas allows you to instantly transition from monitoring to administration via Protocol Quick Links. These links launch your locally installed administrative clients directly from the Device Drawer.

How it Works

The application uses standard URI Schemes registered on your operating system. When you click a link, StacksAtlas triggers a request that your OS handles by launching the associated application:
  • RDP (rdp://): Launches the Windows Remote Desktop Connection client.
  • SSH (ssh://): Opens your default SSH client (e.g., PuTTY, TeraTerm, or Windows Terminal).
  • Telnet (telnet://): Opens your default Telnet client.
  • FTP (ftp://): Opens your default FTP client or Windows Explorer.

Key Features & Security

  • One-Click Connectivity: No need to copy-paste IP addresses between windows.
  • Hygiene Warnings: StacksAtlas provides a deliberate visual warning when launching unencrypted protocols (Telnet/FTP), reminding you that credentials will be sent in plain text.
  • Client Flexibility: Because we use standard URI schemes, the application respects your system's default handler preferences.

Troubleshooting Disconnected Adapters

If an interface you expect to see is missing or marked as "Disconnected":
  • Check physical cable connection.
  • Ensure the adapter is enabled in Windows Network Connections.
  • StacksAtlas shows even disconnected physical adapters, but they cannot be used for active scanning until the hardware reports an "Up" status.