Network Locations
Understanding how Pulse categorizes devices by their network location helps you better visualize and manage your network topology.
Location Types
Pulse categorizes network nodes according to their logical and physical location relative to the host system. Each location type helps you understand how a node is positioned within your overall network architecture.
Why Location Matters
Network locations help determine how devices can be reached as well as what routing and connection node options can be provided.
LOCAL
Devices physically connected to the same internal network (LAN) as the host running Pulse.
- Typically have private IP addresses (192.168.x.x, 10.x.x.x, etc.)
- Directly accessible without routing through external networks
- Often share the same subnet and default gateway
PUBLIC
Devices with directly accessible public IP addresses that are reachable over the internet without any NAT or tunneling.
- Common examples include web servers, cloud instances, and CDN endpoints
- Directly addressable from any internet-connected device
- Often have security measures like firewalls in place
REMOTE_VIA_ROUTER
Devices behind a public-facing router, typically located in a remote site or home network.
- Require port forwarding or NAT traversal to be reached
- Usually communicate through a gateway device that handles NAT translation
- May have limited direct accessibility from outside their local network
VPN_REMOTE
Devices only reachable via a VPN server (also mapped in Pulse).
- Without the VPN connection, these nodes are inaccessible
- Appear to be on the local network when the VPN is connected
- Nodes are only to be classes as VPN_REMOTE if a Split-Tunnel VPN is in use.
CLOUD_PUBLIC
Devices in a cloud-hosted environment that have been assigned public IPs and are directly reachable from the internet.
- Often act as jump-points or front-facing services for cloud infrastructure
- May serve as gateways to internal cloud services
- Typically protected by cloud provider security groups or firewalls
CLOUD_PRIVATE
Devices that exist within a private subnet of a cloud environment, such as AWS, Azure, or GCP.
- A node with CLOUD_PRIVATE location must be routed via a node with CLOUD_PUBLIC location.
- Often part of a virtual private cloud (VC) architPecture
- May use internal DNS naming conventions specific to the cloud provider
Node Connectivity Concepts
Beyond network location, Pulse uses additional attributes to define how nodes connect to and communicate through your network.
Connection Node
The device that a node is directly linked to within the network — whether via wired or wireless connection.
- Defines the immediate upstream connection for the device
- Helps visualize the physical or logical topology of your network
- Often represents a switch, access point, or router
Exit Node
The device through which a node routes outbound traffic beyond its immediate network.
- Typically the default gateway or a routing device responsible for external communication
- Critical for understanding traffic flow and potential bottlenecks
- May be different from the connection node in complex networks
Important Note
Network locations are automatically determined to be LOCAL within the discovery service, however it can be manually adjusted if needed