Testing Your Connection
Torus Echo -the Connectivity Test Service
Once you have configured your VPN connection, you can verify it is working correctly by connecting to the Torus Echo service. This is a dedicated test endpoint that is always available on the Torus network.
Test Endpoint
| Service | Address | Description |
|---|---|---|
| HTTP | http://10.254.16.50/ |
Web page confirming connectivity |
| Telnet Echo | telnet 10.254.16.50 |
Echo service - characters are reflected back |
Testing via Web Browser
The easiest way to test your connection:
- Connect to the Torus VPN using your WireGuard configuration
- Open a web browser
- Navigate to http://10.254.16.50/
- If you see the "Torus Echo - Connection Successful" page, your VPN is working!
Testing via Command Line
Using curl (HTTP)
curl http://10.254.16.50/
Expected output: HTML content with "Connection Successful" message
Using ping
ping 10.254.16.50
Expected output: Replies from 10.254.16.50 with latency typically 100-150ms (varies by location)
Using telnet (Echo Service)
telnet 10.254.16.50
You will see a welcome banner. Any text you type will be echoed back to you. To exit:
- Press
Ctrl+]then typequit - Or
simplyclose the terminal
Troubleshooting
Cannot reach 10.254.16.50
- Check VPN is connected - Verify WireGuard shows "Latest handshake" within the last
2fewminutesminutes. Even if the client shows connected...it could be lying to you :) - Check your AllowedIPs - Must include
10.254.16.0/24(Note: this subnet is the Torus overlay). - Firewall rules - Ensure your local
firewallgateway device allows traffic to 10.254.16.0/24
High latency
- The echo server is located in
DubaiDubai, UAE - expect 100-200ms250ms from Europe/US - If latency exceeds
300ms,500ms, check your internet connectionqualityquality. Some ping tools time out at 1000ms (1 second), so if you get 'no reply from' or' unreachable', then try to increase your timeout.
Still not working?
Contact support via the Support page or(Forum postwill inbe thecoming Forum.2026)
Technical Details
The Torus Echo service runs on an isolated network segment behind a Mikrotik Cloud Hosted Router (CHR). It provides:
- HTTP (port 80): nginx web server with connectivity confirmation page
- Telnet (port 23): Secure echo daemon - characters are
reflected back,reflected, no shell access
IP Address 10.254.16.50 is permanently reserved for this service and will never be allocated to users.