keenetic-troubleshoot

Working out what is wrong with the network

Start from the symptom and work outward. Each step below either finds the fault or rules out a whole class of them, so do not skip ahead.

"The internet is down"

1. Is it the internet or the router?

get_internet_status

The flags separate the cases:

• internet: false, gatewayAccessible: false - the link to the provider is down. Go to step 2.
• gatewayAccessible: true, dnsAccessible: false - the connection is up and DNS is the problem. Go to step 3.
• captiveAccessible: false on a hotel or public uplink - a captive portal is intercepting traffic.
• everything true - the router is fine and the problem is on one device. Go to the device section.

2. The uplink itself

list_interfaces { "kind": "wan" }

link: "down" means no signal on the physical port: cable, provider, or modem. link: "up" with state: "down" means the interface is administratively disabled, which someone or something turned off.

Check which link actually carries traffic:

list_routes { "kind": "default" }

If the default route points at a VPN tunnel rather than the physical WAN, and that tunnel is down, the internet is unreachable even though the provider is fine. That is a common cause and easy to miss.

3. DNS

rci_call { "method": "GET", "path": "show/dns-proxy" }

Then confirm the tunnel or upstream the DNS traffic depends on is actually up with list_interfaces { "kind": "vpn" }.

"One device cannot get online"

get_device { "mac": "..." }

Read in this order:

• blocked: true - access is denied for it. That is the answer.
• schedule set - it may be outside its allowed hours.
• policy set - it leaves through a specific link. Check that link is up with list_interfaces { "kind": "vpn" }.
• active: false - the router has not seen it recently. This is a connectivity problem between the device and the router, not a policy problem.

"Wi-Fi is bad"

get_wifi_status