Sensor - Network Diagnostic
Network Diagnostic setting is accessible under Settings > Network Diagnostic

Network diagnostics involve using specific tools and techniques to identify and resolve connectivity issues, measure performance, and ensure proper communication across devices. Below are some commonly used tools and their applications:
1. Ping Test
Purpose:
To verify network connectivity between two devices and measure the latency (response time).
How It Works:
The ping command sends ICMP (Internet Control Message Protocol) Echo Requests to a target address and listens for Echo Replies.
Steps to Perform:
- Clicking on the Ping Test tab.
- Run the Ping followed by the target IP address or hostname:

- Analyze the output:
- Successful Reply: Indicates connectivity.
- Packet Loss: Signifies a problem in the network.
- Latency (ms): Measures the time taken for packets to travel to the destination and back.
Key Metrics:
- Latency (ms): Lower values indicate faster response times.
- Packet Loss (%): Any packet loss suggests network issues.
2. Trace Route
Purpose:
To identify the path taken by packets to reach their destination and pinpoint delays or failures in the route.
How It Works:
The traceroute command (Linux/macOS) sends packets with increasing Time-to-Live (TTL) values to record each hop.
Steps to Perform:
- Clicking on the Trace Route tab.
- Run the Trace Route followed by the target IP address:

- Examine the output:
- Each line represents a network device (hop).
- Look for high latency or "request timed out" messages to identify problematic hops.
Use Case:
- Troubleshooting slow network performance.
- Identifying a specific network device causing delays.
3. Telnet
Purpose:
To test connectivity to a specific port on a remote device and troubleshoot services running on that port.
How It Works:
The telnet command establishes a connection to a target IP and port to verify accessibility.
Steps to Perform:
- Clicking on the Telnet tab.
- Run the telnet with the target IP and port:

- Interpret the result:
- Successful Connection: Indicates the port is open and accessible.
- Connection Refused/Timeout: Indicates the port is closed or blocked by a firewall.
Use Case:
- Verifying access to services like HTTP (port 80), HTTPS (port 443), or SSH (port 22).
- Debugging blocked or inaccessible ports.