Settings

Equipment Device RADIUS Authentication

Grant Managers and NOC staff RADIUS login access to MikroTik devices with their existing ISPbills credentials.

The Equipment Device Auth page lets a Group Admin grant Managers and NOC users permission to log in to MikroTik routers through FreeRADIUS. Staff use their ISPbills email address and existing ISPbills password; no separate device password is created.

Before You Begin

Confirm that:

  • RADIUS service is enabled for your ISPbills account.
  • Each target MikroTik router is registered under the same group and has working RouterOS API credentials.
  • The router can reach the RADIUS server address provided for your account.
  • The required RADIUS authentication and accounting ports are allowed between the router and server.
  • The Manager or NOC account already exists in ISPbills.

This feature gives staff a login path to network equipment. Grant it only to trusted staff, protect their ISPbills accounts with appropriate security controls and revoke access promptly when their duties change.

Access the Page

Open Settings → Equipment Device Auth.

Role Access
Group Admin or Developer View staff, grant or revoke access and push router configuration
Manager Read-only view for their group
NOC Read-only view after Device Access has been granted
Other roles No access

Only Manager and NOC accounts in the Group Admin's group appear in the table.

Grant Device Access

  1. Find the staff member in Managers & NOC Users.
  2. Click Grant Access.
  3. Confirm that Device Access changes to Granted.

ISPbills grants device access for the staff account. It does not create or display a separate device password.

Push Configuration to Routers

After granting access, click Push Config to Routers. ISPbills connects to every router in the group with working API credentials and reports an individual OK or Error result.

For each reachable router, ISPbills:

  1. Finds the RADIUS entry whose address matches the configured server address.
  2. Adds login to that entry's existing services, or creates an entry with hotspot,ppp,login when none matches.
  3. Enables RouterOS user RADIUS authentication with /user/aaa use-radius=yes.

The push action changes every eligible MikroTik router in the group. Review the per-router results; one router failing does not prevent results from being returned for the others.

Use the RADIUS address and ports shown for your account. If a push reports OK but login fails, compare the router's RADIUS settings with those values or contact ISPbills support.

Staff Login

After both access grant and successful router configuration, staff log in to the MikroTik device with:

Router login field Value
Username Their ISPbills email address
Password Their current ISPbills password

If the ISPbills password is changed later, grant access again before expecting the new password to work on devices.

Revoke Device Access

  1. Find the staff member whose status is Granted.
  2. Click Revoke.
  3. Confirm the prompt.

Revocation removes the staff member's device access. It does not remove the router's general RADIUS configuration or disable /user/aaa use-radius=yes.

Troubleshooting

Symptom Check
No staff are listed Create a Manager or NOC user under the same group first.
No routers with API credentials found Add valid API credentials to the group's MikroTik routers.
Router result says Connection failed Check the router host, API username/password, API port and network reachability.
Push succeeds but login fails Check router reachability and compare its RADIUS address and ports with the values provided for your account.
Existing ISPbills password does not work Revoke and grant access again, then retry.
NOC cannot open the page A Group Admin must first grant Device Access.