This guide explains how to run a bounded ICMP check and decide which DC++ hub diagnostic should follow it.
Usage
- Open Ping Tool and enter a public hostname, IP address, or hub URL in Host Or Address.
- Select Run Ping. A non-admin visitor may also need to complete CAPTCHA.
- Review resolved addresses, packet counts, loss, latency, and the bounded raw response.
Concrete Example
Suppose dchub://hub.example.net:411 stopped appearing online after a DNS change. Submit the full address; the form extracts hub.example.net. Four received packets with 0% loss show that the resolved host answered ICMP from the hublist server, but they do not test port 411.
Interpretation
Compare transmitted and received packets first. Partial loss can indicate congestion, filtering, or load. Minimum, average, maximum, and deviation values describe only the returned probes. Confirm that the resolved IPv4 or IPv6 address is the address you intended to test.
Troubleshooting
- DNS Failure: Check the hostname, delegation, record type, and TTL with DNS Dig.
- 100% Loss: The host or an upstream firewall may block ICMP while the hub remains healthy.
- Private Target Blocked: Use the public address; LAN, loopback, reserved, and documentation ranges are rejected.
- Ping Works, Hub Fails: Test the advertised port with TCP Connect, inspect secure endpoints with TLS Certificate, and verify the selected Direct Connect protocol with Protocol Test.
Icon Reference
| Icon | Label | What It Does |
|---|---|---|
| Run Ping | Run Ping submits the public host for the bounded ICMP check. | |
| Reachable | Reachable marks a result that received the expected ICMP replies. | |
| Check Output | Check Output marks loss, incomplete replies, or a result that needs another diagnostic. | |
| Open Help | Open Help opens this guide from the Ping tool panel. |