MikroTik + RADIUS
MikroTik hotspot
MikroTik is common for hotspot and wireless edge. Local user lists don’t scale for ops or 5651 archives. Making MikroTik a RADIUS client and collecting identity/logs in IDNET scales without rip-and-replace.
RouterOS hotspot + external RADIUS
MikroTik hotspot authenticates against external RADIUS. User creation, quotas and time live in IDNET; forwarding stays on MikroTik.
One panel, many sites
Multiple branches or hotel AP groups can share one RADIUS. Central reporting and log archive reduce per-device admin.
The right boundary for 5651
MikroTik can emit local logs; legal archive and identity binding prefer central signed storage—IDNET provides that layer.
When to add APs
Only for coverage or capacity. Identity/logging alone rarely forces hardware swap—evaluate RADIUS first.
Frequently asked questions
Which MikroTik models work?
RouterOS devices with hotspot and RADIUS client features typically qualify. Model and version are verified in discovery.
Can existing users migrate?
Import or phased cutover is planned—critical accounts first, guest vouchers later.
Is MikroTik the only client?
No. IDNET speaks standard RADIUS; MikroTik is simply one of the most common clients in Turkey.
IDNET Radius Manager
This page targets one search intent. See the main product page for full scope and technical detail.
/en/software/idnet-radius-manager ↗