RADIUS NAS Identity for Multiple MikroTik Gateways

This guide covers RADIUS NAS identity. Start with the checks below. Then compare your result with the example before changing a live service. Central authentication requires clear gateway identification. Record how each intended access device is recognized so that a failure at one site is not confused with another router's request.

RADIUS NAS identity: practical checks

1. Inventory gateway addresses and the identifiers used by the deployed RADIUS setup.
2. Confirm the request originates from the expected device and path.
3. Keep shared secrets private and separate from diagnostic summaries.

RADIUS NAS identity: a working example

A gateway whose source address changes may no longer match the expected server configuration. Diagnose the request identity before recreating customer accounts.

First, write down the starting state and the expected result. Then make one controlled change. Next, compare the result with the example above. Finally, record what changed and who should follow up. Keep private account details out of shared notes.

Where LinkDesk fits

LinkDesk includes local PPPoE workflows and a FreeRADIUS bridge. These require deployment testing. Enforced PPPoE or RADIUS data quotas and strict global simultaneous-session enforcement for RADIUS PPPoE are not included in the documented current scope.

For the tool or product details behind this guide, see MikroTik RADIUS documentation. The checklist and example above are WayaDesk’s operating guidance.