Appearance
NAS Devices
A Network Access Server (NAS) is the router, BNG, or access concentrator that sends subscriber authentication and accounting requests to Dream Radius. Register every device that serves your customers before pointing it at the RADIUS server.
Open NAS Devices from the sidebar to add, edit, monitor, or remove device records. NAS records are isolated to the applicable ISP, so one tenant cannot use another tenant's router configuration.
Before you add a NAS
Have these values ready from the router and server configuration:
| Value | What it is |
|---|---|
| NAS name | A recognisable label, such as Karachi Core BNG. |
| NAS IP address | The router or BNG address that sends RADIUS traffic. It must be unique. |
| RADIUS shared secret | The secret that must exactly match the secret configured on the router. |
| Vendor | MikroTik, NetElastic, Cisco, or Other. |
| Authentication port | The RADIUS-server UDP port used for Access-Request traffic; normally 1812. |
| Accounting port | The RADIUS-server UDP port used for accounting traffic; normally 1813. |
| CoA / Disconnect port | The port on the router that accepts Change of Authorization or Disconnect requests; normally 3799. |
Ports have different destinations
Authentication and Accounting are ports on the Dream Radius server that the NAS sends traffic to. CoA / Disconnect is a port on the NAS itself that Dream Radius contacts to disconnect or re-authorize a subscriber. Do not enter the same values without confirming the router configuration.
Add a NAS
- Go to NAS Devices and select Add NAS.
- Enter the device name, IP address, vendor, and RADIUS shared secret.
- Confirm the authentication and accounting ports match the RADIUS listeners on this server. The defaults are
1812and1813. - Enter the router's CoA / Disconnect port, normally
3799. - Configure router API access only when it is needed for the selected vendor.
- Save the device, then configure the router to use this server address, matching ports, and the same shared secret.
- Open the device status to verify connectivity before onboarding live subscribers.
The device IP is the identity used to recognize the NAS. Updating it or the shared secret requires the corresponding router-side change at the same time, otherwise RADIUS requests will fail.
Router API access
MikroTik and Cisco records can optionally use a router management API. Enable API access only when it is required, then enter the API username, password, and port. The default MikroTik API port is 8728.
The router API credentials are separate from the RADIUS shared secret. They are also separate from any NetElastic netVision credentials. Treat all three as sensitive credentials and give the integration account only the permissions it needs.
When editing a NAS, leave a masked API password blank to retain the stored value. Enter a new value only when rotating the credential.
NetElastic and live utilization
For a NetElastic BNG, the optional netVision settings enable live-utilization data. The netVision URL is the address of the netVision management server—not the BNG's own address—and normally points to a different host.
Provide the netVision URL, BNG ID, username, and password together. Use the BNG discovery control in the NAS form to select the correct BNG from the management server. These credentials are distinct from both the BNG management credentials and the RADIUS shared secret.
Use the insecure-TLS option only when the netVision server has a self-signed or invalid certificate and you understand the risk. Prefer a valid certificate or a trusted reverse proxy for production use.
Check NAS status
The NAS list shows each device's live status. Select its status indicator for a detailed, on-demand check. It can report:
- ICMP reachability to the NAS;
- the configured router management API port, when API access is enabled;
- the router's CoA / Disconnect port and shared-secret response;
- the Dream Radius authentication and accounting listener ports.
These checks run when requested, so the result is not a cached health value. A reachable router with a failed RADIUS authentication check usually indicates a firewall, listener-port, or shared-secret mismatch. A failed CoA check can prevent manual disconnects and package-change reauthorization even while logins still work.
Port bindings
Administrators can open Port Bindings to review restrictions configured on reseller and customer records. A reseller binding can allow or block authentication through named NAS interfaces, and a customer can override its parent reseller's binding where permitted.
Copy interface names exactly as the NAS reports them in NAS-Port-Id; the match is exact. Do not guess a value such as ether2 if the auth log shows a different spelling or encoding.
Use bindings sparingly and test with one customer first. An incorrect binding can reject every affected subscriber at authentication time.
Interface bindings
Interface Bindings are an administrator-only control for reserving or blocking a specific interface on one NAS. Create either a whitelist or blacklist for the interface, select the resellers it applies to, and optionally define customer exceptions.
These rules are independent from per-reseller port bindings. A login must satisfy every applicable rule, so review existing port bindings before adding an interface rule. Rules are scoped to one NAS and one exact interface name; an interface with no rule remains unrestricted.
Update or remove a NAS
Edit a NAS when its address, ports, vendor settings, or credentials change. Validate live status immediately after saving. Removing a NAS deletes its device record; first make sure no reseller access policy or production router still relies on it.
Safe rollout
Add and verify a new NAS using a test subscriber before migrating a larger access network. Confirm an Access-Accept, an accounting start/update, and a Disconnect or CoA request before considering the setup complete.