Skip to content

Device login (RADIUS)

Let each engineer log into devices (Mikrotik, Juniper, Cisco, Fortigate, Huawei) over SSH, WinBox or console using the same platform account — no shared password and no per-device user accounts. The device asks Version2 whether the login is valid; Version2 answers.

Who can do this: the Manager creates the users and configures the devices. Each RADIUS-only user sees and changes their own password in My RADIUS account.

  • The user is created in the panel (under RADIUS > Users) and sets the password on first access, through the e-mail invite. The Manager never sees the password.
  • On the device, the person logs in with the RADIUS username and the same password as the panel.
  • The credential stays only on Version2. The device sends the login request (RADIUS) to Version2, which checks it and answers accept/reject.
  • There are two ways to reach Version2 (pick one per device):
    • Local proxy: the device points RADIUS at the proxy on your network, which carries the request to Version2 over the tunnel. Useful when the device should not talk to the internet directly.
    • Direct to the platform: the device points at 38.254.8.5, ports 1812 (authentication) and 1813 (accounting). In this mode, register the device source IPs under RADIUS > Devices > Point directly to the platform and use the tenant secret shown there.

Each mode has its own shared secret: per proxy, on the proxy; in direct mode, the tenant secret. Keep it safe — it is what proves the request comes from your account.

  1. In the menu, open RADIUS > Users and click New user. Enter name, e-mail, the profile (read, write or full) and the device groups. The person gets the invite to set the password.
  2. Open RADIUS > Devices. For local proxy, find each proxy’s secret there. For direct, open the Point directly to the platform card, click Enable direct mode, Reveal the tenant secret and enter the source IPs/CIDR of the devices.
  3. Configure each device as in the snippets below, replacing ADDRESS with the proxy IP (proxy mode) or 38.254.8.5 (direct mode), and SECRET with the matching shared secret.
  4. Test the login with a real user. Attempts show up under RADIUS > Logs.

This is for administrative login to the device — operator access over SSH, WinBox, console or the web panel. It is not for authenticating subscribers (PPPoE), hotspot or client VPN: those use a separate RADIUS service on the same device, apart from this one.

Supported protocols: PAP and MS-CHAPv2. The snippets below are the essentials; confirm the exact syntax in your version’s documentation.

/radius add service=login address=ADDRESS secret=SECRET
/user aaa set use-radius=yes

In WinBox, the same lives under IP > RADIUS (service login) and System > Users > AAA (tick Use RADIUS).

set system radius-server ADDRESS secret "SECRET"
set system radius-server ADDRESS port 1812
set system authentication-order [ radius password ]

Also define a local user template (for example, a login class) for the RADIUS-authenticated accounts, per your policy.

aaa new-model
radius server V2
address ipv4 ADDRESS auth-port 1812 acct-port 1813
key SECRET
aaa authentication login default group radius local
aaa authorization exec default group radius local

The trailing local keeps access through a local account if Version2 becomes unreachable.

config user radius
edit "V2"
set server "ADDRESS"
set secret SECRET
set auth-type auto
next
end
config user group
edit "V2-admins"
set member "V2"
next
end
config system admin
edit "radius"
set remote-auth enable
set wildcard enable
set remote-group "V2-admins"
set accprofile "super_admin"
next
end

auth-type auto tries PAP and MS-CHAPv2. wildcard enable lets any user validated by Version2 log in through this entry; accprofile sets the permissions. Local admin accounts keep working if Version2 becomes unreachable.

radius-server template v2
radius-server authentication ADDRESS 1812
radius-server shared-key cipher SECRET
#
aaa
authentication-scheme sch-radius
authentication-mode radius
domain default
authentication-scheme sch-radius
radius-server v2

The engineer logs into the device with the platform username and password. Changed the password in the panel? It is valid on both ends right away. Left the account (removed from the team)? The device login stops working. Every attempt, accepted or rejected, is listed under RADIUS > Logs.

  • Everyone is rejected: check that the secret on the device matches the one in the panel (proxy or tenant) and that the address/port are right (1812 for authentication). In direct mode, confirm the device source IP is registered under Point directly to the platform.
  • Only one person is rejected: check the reason under RADIUS > Logs. It may be a wrong password, a blocked account, too many attempts in a row (there is a per-minute limit), or the person no longer being on the team.
  • Changed the password but the old one still works: it does not happen — the change updates both ends in the same operation. Sessions already open on the device do not drop on their own; close them on the device if needed.
  • Never put the secret in a log, ticket or screenshot. If it leaks, generate a new one in the panel.