Skip to main content
Sherlock Suite

Product documentation

Which product are you working with?

Choose a product to see its guides and setup instructions.

All documentation

Maps, gateways and VLANs

Explore your networks and devices on a visual canvas. Define subnets, gateways, and VLAN labels to make the map easier to understand.

Explore the map

Open Network map to see networks and gateway roles. Select a network to view a bounded page of device nodes. Use network and VLAN filters to narrow the view. Zoom, fit the canvas, or switch to the accessible list for keyboard-friendly navigation.

Dashed gateway and subnet lines describe logical membership. They do not prove that devices are directly connected by a cable. Reported LLDP, CDP, and forwarding observations are labelled separately.

Name networks and VLANs

  1. Open Settings > Networks, gateways and VLANs.
  2. Choose an existing subnet or add a network definition for a scanner.
  3. Set a descriptive network name and its private IPv4 subnet.
  4. Optionally enter a VLAN ID from 1 through 4094 and a VLAN name.
  5. Save the definition, then open it in the map.

Network administrators manage these definitions. Existing discovery ranges also appear as networks.

Set or detect a gateway

Recent scanners report local IPv4 gateway evidence from their own interfaces. A configured gateway override takes precedence over detected evidence. Leave the override blank to use available detection.

Gateway detection is limited to the scanner's own networks and expires after 24 hours. A remote VLAN's gateway usually needs an explicit definition. Network does not guess a gateway from an address ending in .1. A gateway node describes its routing role, not guaranteed reachability.

Discover across VLANs

A scanner must have routing and firewall access to the configured target range. Defining a VLAN does not configure a switch, create a route, or bypass isolation.

Adding a definition alone does not expand scanning. The optional Add this subnet to the scanner discovery ranges checkbox explicitly adds scope, subject to the eight-range and 1,024-address limits.

Reported connections

Optional SNMPv3 monitoring can collect supported LLDP/CDP neighbor and learned MAC-forwarding observations. Results depend on equipment support, configuration, and scan visibility. Learned forwarding is not proof of a direct cable; bridge-table port identifiers may differ from physical port labels.

Partial or old observations remain labelled. See monitoring setup to configure read-only SNMPv3.