> ## Documentation Index
> Fetch the complete documentation index at: https://docs.wifipadi.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Looking after a gateway
> What you can do to a router once it is online: reboot, back up, update, re-provision, and monitor your access points.
[Onboarding a gateway](/gateway-setup) ends when the status reads **Online**. This page is everything after that.
Go to **Gateways** and select a gateway to open its page.
## What the status means
| Status | What it means |
| ---------------- | --------------------------------------------------------------- |
| **Online** | Checked in recently. Selling. |
| **Offline** | Has not checked in. Power, internet line, or the router itself. |
| **Provisioning** | Mid-install. Give it a minute or two. |
| **Failed** | The install did not finish. Re-run the install command. |
The gateway page also shows **last contact** — the last time the device reached us at all. That is a different question from status, and it is the one to read when you are deciding whether a router is dead or merely idle.
## Remote actions
These run over the WifiPadi tunnel. You do not need to be on site or plugged into anything.
| Action | What it does | Available on |
| --------------------- | -------------------------------------------------------------------------------------------- | ------------ |
| **Reboot** | Restarts the router. First thing to try when a site is behaving oddly. | Both |
| **Config backup** | Pulls a copy of the router's configuration and stores it. Download it from the gateway page. | Both |
| **Agent update** | Pushes the current WifiPadi software to an already-installed router. | Nano Pi |
| **Re-provision** | Issues a fresh install command. How a working gateway picks up installer changes. | Both |
| **Access point scan** | Read-only sweep of the local network to find access points. Changes nothing. | Nano Pi |
**Agent update** is the one to reach for after we ship an enforcement change — fair-use shaping, for instance. It is not a reboot, guests stay connected, and it takes seconds. If a gateway is behaving in a way this guide does not describe, run it before you contact support.
## Access points
Most venues run one gateway and several access points — the boxes on the ceiling actually broadcasting the WiFi. WifiPadi can watch them for you and tell you when one dies.
On a Nano Pi gateway, select **Access point scan**. It sweeps the local network and lists what it found, each ranked by how likely it is to be an access point rather than somebody's phone.
Register the ones that really are access points. A device in bridge mode looks exactly like a laptop from the network's point of view, so the ranking is a suggestion and you are the one who decides.
*Block C stairwell* beats *EAP225-2*. When one goes down at 9pm, the name is what tells you where to walk.
Once registered, the gateway pings each access point and records outages. The gateway page lists them with their current state and their outage history.
| What you see | What it means |
| ---------------------- | --------------------------------------------------------------------------------------------------------------- |
| **Online** | Replying to ping. |
| **Offline** | No reply. Power, cabling, or ICMP replies switched off on the AP itself. |
| **No round-trip time** | It answers ARP but not ping — powered and cabled, but it cannot be timed. Enable ICMP on the AP to get timings. |
## Remote Winbox (MikroTik)
You can reach a MikroTik's Winbox port through the WifiPadi tunnel without exposing it to the internet.
On the gateway page, select **Open Remote Winbox**. You get a temporary address and port to point Winbox at, and a short wait while the route comes up. Access is time-boxed and closes itself.
This is a real management session on a live router. Changes you make in Winbox to the hotspot, RADIUS or firewall configuration can stop guests being able to buy or use access, and WifiPadi will not put them back. Take a **Config backup** first.
## Moving or renaming a gateway
Use the edit action on the gateway page to rename it or move it to another location. Renaming is cosmetic. Moving reassigns which location's revenue and reporting it contributes to from that moment on; history stays where it was earned.
## Troubleshooting
Check power and the WAN cable first — most of these are the internet line at the venue, not the router. If the line is fine, **Reboot** from the dashboard. If the reboot never lands, the device is not reaching us at all and someone has to look at it.
Run **Agent update**, then **Reboot**. This combination clears the case where the captive portal service came up before the network was ready and has been sitting in a half-started state — the dashboard still shows green throughout, because the rest of the device is checking in normally.
That is what **Re-provision** is for, and it is safe to run on a working gateway. Use it after we change the installer — for example when a new payment domain has to be added to the list of sites guests can reach before paying.
The AP is probably fine and its ICMP replies are switched off, which some access points do by default. Check the WiFi on site; if it is genuinely working, enable ICMP on the AP or remove it from monitoring rather than leaving a false alarm in place.