Skip to main content

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/KevinCruz-cell/Redes-de-comunicaciones-/llms.txt

Use this file to discover all available pages before exploring further.

The diagnostics page lets you run standard network troubleshooting tools directly on the router without opening a terminal. Commands are executed on the router over SSH, so results show connectivity and DNS resolution from the router’s perspective — not the web server’s.

​
Accessing diagnostics

Navigate to /router3/diagnosticos. You must be logged in to access this page.

​
Available tools

Ping

Tests reachability of a host by sending ICMP packets. Reports round-trip time and packet loss.

Traceroute

Maps each hop between the router and the destination. Output is numeric — no DNS lookups are performed during the trace.

Nslookup

Resolves a hostname or IP address using the router’s configured DNS servers.

​
How to run a diagnostic

1

Open the diagnostics page

Go to /router3/diagnosticos in your browser.
2

Select a tool

Choose Ping, Traceroute, or Nslookup from the tool selector.
3

Enter a destination

Type a hostname (e.g. google.com) or an IP address (e.g. 8.8.8.8) into the destination field. The destination field is required.
4

Run the command

Submit the form. The application opens an SSH session to the router, runs the command, and returns the raw text output.

​
Command reference

Each tool maps to a specific shell command executed on the router.
Command: ping -c 5 -W 2 <destination>Sends 5 ICMP echo requests with a 2-second wait timeout per packet.
PING google.com (142.250.80.46): 56 data bytes
64 bytes from 142.250.80.46: seq=0 ttl=116 time=11.243 ms
64 bytes from 142.250.80.46: seq=1 ttl=116 time=10.891 ms
64 bytes from 142.250.80.46: seq=2 ttl=116 time=11.102 ms
64 bytes from 142.250.80.46: seq=3 ttl=116 time=10.978 ms
64 bytes from 142.250.80.46: seq=4 ttl=116 time=11.034 ms

--- google.com ping statistics ---
5 packets transmitted, 5 packets received, 0% packet loss
round-trip min/avg/max = 10.891/11.049/11.243 ms
  • -c 5 — send exactly 5 packets
  • -W 2 — wait up to 2 seconds for each reply before marking a packet lost

​
Input validation

The server validates both fields before opening an SSH connection:
FieldRule
accionMust be one of ping, traceroute, or nslookup
destinoRequired; accepts hostnames or IP addresses
If validation fails, the API returns a 422 response with details about which field is invalid.

​
Understanding results

All output comes from the router, not the web server. A successful ping result means the router can reach the destination. If the router is behind NAT or has restricted routing, results may differ from what you see on your local machine.
Traceroute may show * * * for hops where intermediate routers drop probe packets (ICMP filtering). This does not necessarily mean connectivity is broken at that hop.
Use nslookup first to confirm the router is resolving DNS correctly before using ping or traceroute. If nslookup fails but ping with an IP succeeds, the issue is DNS configuration on the router.

Build docs developers (and LLMs) love

Get started for freeTalk to us