> ## Documentation Index
> Fetch the complete documentation index at: https://docs.centipidbilling.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Routers and NAS

> Understand the router inventory, service state, monitoring, and available operator actions.

# Manage network access servers

Centipid Billing uses a NAS record to represent a MikroTik/router participating in subscriber authentication, accounting, captive access, and monitoring. Open **Network → Devices → Routers** to see the router inventory.

## What the inventory shows

The router list summarizes registered devices and live/recent state. A router detail page can expose:

* identity, RouterOS/network identifiers, and service configuration;
* online/reachability and WireGuard transport state;
* PPPoE and Hotspot service state and bridge ports;
* anti-sharing, accounting interval, captive template, and support settings;
* live bandwidth, system metrics, top consumers, trends, and daily collections;
* monitoring state, diagnostics, and remediation findings;
* maintenance mode and scheduled router actions.

Live metrics depend on a reachable router and the configured management path. A missing live card does not prove the subscriber service itself is down; compare reachability, RADIUS sessions, and the device's local state.

## Router actions

Depending on current state and permission, the detail page can:

* check status or run diagnostics;
* reconnect WireGuard or rotate its port;
* add/remove monitoring;
* reboot or reprovision;
* change router identity;
* redownload Hotspot files;
* regenerate Winbox access;
* add fallback RADIUS;
* synchronize router time and walled-garden rules;
* enable/disable Hotspot, anti-sharing, Winbox, or maintenance mode;
* adjust accounting time, captive portal, support number, and port settings;
* create/delete router schedules;
* remove the NAS through an OTP-protected workflow.

These actions are not interchangeable. Run diagnostics before reprovisioning; use reconnect/port rotation for transport issues; use walled-garden sync for captive payment reachability; and use full reprovision only when the existing configuration is known to be incomplete or incompatible.

## Safe operating sequence

1. Confirm the router identity and the ISP.
2. Check reachability and the time of the last successful signal.
3. Review affected services and subscriber sessions.
4. Run diagnostics.
5. Apply one targeted remediation.
6. Wait for current status/metrics to refresh.
7. Test authentication and accounting from a controlled subscriber.
8. Record what changed and the result.

## Maintenance mode

Maintenance mode provides a controlled subscriber-facing state during planned work. Configure the support contact and expected message before enabling it. Maintenance mode does not replace change planning, router backup, or a rollback procedure.

## Removing a router

Router deletion is high impact and requires action verification. Before removal:

* move or disable subscribers/packages bound to the NAS;
* confirm no active sessions or binding records still depend on it;
* preserve required router configuration and monitoring context;
* understand the effects on WireGuard, monitoring, captive files, and access paths;
* enter the action OTP only in the application's confirmation flow.

Prefer leaving an offline historical device disabled until dependencies are understood rather than deleting it immediately.

See [Router provisioning](/network/router-provisioning), [Router health](/network/router-health), and [Network troubleshooting](/network/troubleshooting).