Gateway Diagnostics

The Diagnostics (Gateway v14+) tab provides built-in tools for investigating connectivity problems, validating DNS resolution, and monitoring live network activity all running directly on the gateway. Because these tests execute at the network edge rather than from a client device, they give a more accurate and authoritative picture of what's actually happening on your network.

To get started, select a tool from the Diagnostic Tool dropdown. Each tool loads its own fields and output dynamically.


DNS Query

Tests whether the gateway can successfully resolve a domain name using its configured DNS servers. Useful for verifying that your resolver settings are working as expected, or for diagnosing why a specific domain isn't reachable.

FieldDescription
Domain NameThe domain to resolve (e.g., example.com). The gateway returns the resolved IP address or the reason for failure.

💡 Use this tool to validate Split DNS behavior. If a domain should be resolving through an internal DNS server but isn't, DNS Query will help you confirm whether the gateway is routing the query correctly.

Current Network Activity

Provides a real-time view of network usage on a selected interface, including live bandwidth figures and a per-flow breakdown of active connections.

FieldDescription
InterfaceThe interface to monitor.
IPOptional. Filter results by source or destination IP to narrow down activity.

Once running, the tool displays:

  • Download / Upload Rate — Live bandwidth consumption
  • Total Transferred Volume — Cumulative data since the session started
  • Per-Flow Table — Source and destination IP, protocol, usage volume, and real-time speed per connection

💡 Use this tool to identify traffic anomalies, spot unexpected bandwidth consumers, or verify that filtering policies are having the intended effect on a specific interface.

Ping

Sends ICMP Echo Requests from the gateway to a remote host and reports back response times and reachability. A straightforward way to confirm whether a destination is accessible from the gateway's perspective.

FieldDescription
IP Address or DomainThe hostname or IP address to test (e.g., 8.8.8.8, example.com).

Traceroute

Maps the full path a packet takes from the gateway to a destination, showing each intermediate hop along with its associated latency. Useful for identifying where delays or failures are occurring in the routing path.

FieldDescription
IP Address or DomainThe remote host or IP address to trace.

💡 If Ping confirms a destination is unreachable but doesn't tell you why, Traceroute will help you pinpoint exactly where the path breaks down.

Updated

Was this article helpful?

0 out of 1 found this helpful

Have more questions? Submit a request

Comments

0 comments

Please sign in to leave a comment.