Skip to content

FreeRADIUS ​

Dream Radius uses FreeRADIUS as the RADIUS service between your NAS devices and the customer, package, policy, and accounting data held in the application. Operators normally manage subscribers, packages, policies, and NAS devices through the panel; they should not edit FreeRADIUS configuration files for routine customer work.

What happens when a customer connects ​

  1. The NAS sends an Access-Request to Dream Radius on the configured authentication port, normally UDP 1812.
  2. FreeRADIUS validates the NAS and shared secret, then checks the customer's account, service state, package policy, and applicable network restrictions.
  3. If approved, FreeRADIUS returns an Access-Accept with the RADIUS reply attributes required for the package—such as speed, addressing, or session controls. If not, it returns a reject with the relevant reason.
  4. The NAS sends Accounting-Start, interim updates, and Accounting-Stop packets to the accounting port, normally UDP 1813.
  5. Dream Radius records session timing, addresses, traffic, and authentication outcomes for the customer and reporting views.

The NAS IP address, RADIUS ports, and shared secret must match the NAS record in Dream Radius. A mismatch prevents the request from being trusted or processed correctly.

Authorization sources ​

Dream Radius builds authorization from the data you manage in the panel:

  • Customers provide the username, credential, connection settings, account status, and expiry.
  • Packages provide the billing term and select a policy.
  • Policies provide RADIUS check and reply attributes, such as vendor speed limits or session rules.
  • Static IP assignments and IP-pool settings add the appropriate address behavior.
  • NAS and interface restrictions determine where the customer may authenticate.

This is why a package or policy change should be made through the CRM rather than by manually editing RADIUS database rows. The application keeps billing, expiry, customer status, and RADIUS data aligned.

Authentication outcomes ​

An Access-Accept means the credentials and account rules passed. A rejection can be caused by an incorrect password, disabled or deleted account, expired service, an unassigned/invalid package, a NAS or interface restriction, or an unmatched NAS shared secret.

Use Logs & Reports → Auth Logs to investigate accepted and rejected attempts. Check the username, reply, reason, MAC address, NAS port, date, and NAS device before changing a customer record. For an interface-related issue, copy the reported NAS-Port-Id exactly when reviewing a NAS binding.

Accounting and online state ​

Accounting packets create and update the session records used by Online Users, customer details, Usage Summary, and Session History. Interim updates are important: they keep online status and usage current while a session remains open.

If a customer appears online after disconnecting, inspect Session History and the NAS status first. Dream Radius classifies sessions without a recent accounting update as stale and cleans them up automatically; an on-demand stale-session cleanup is available to authorized operators when needed.

Disconnect and change of authorization ​

Dream Radius sends Disconnect or CoA requests to the NAS's configured CoA port, normally UDP 3799. This is used when a live customer must re-authenticate immediately—for example after a manual disconnect, a service-status change, a password or static-IP update, or a package change.

A same-package renewal does not need a disconnect because the active policy is unchanged. A package change may disconnect the customer so the NAS requests the updated policy on the next login.

Review Logs & Reports → CoA Logs when a disconnect did not take effect. The usual checks are the NAS address, CoA port, firewall path, router support, and shared secret.

Configure a NAS safely ​

For each router or BNG, configure:

Router-side settingDream Radius value
RADIUS server addressThe Dream Radius server's reachable IP or hostname.
Authentication destination portThe NAS record's Authentication Port (normally 1812).
Accounting destination portThe NAS record's Accounting Port (normally 1813).
Shared secretThe exact Shared Secret on the NAS record.
CoA / Disconnect listenerThe NAS record's CoA / Disconnect Port (normally 3799) on the router.

After saving the NAS record, use its status panel to test reachability and configured ports. Then test with one known subscriber and confirm both an authentication event and accounting record are visible in the panel.

Operational checks ​

When subscribers cannot authenticate, use this order:

  1. Confirm the NAS is online and the RADIUS authentication listener is reachable.
  2. Verify the NAS IP, RADIUS ports, and shared secret on both sides.
  3. Check Auth Logs for the response and reason.
  4. Check the customer is active, not expired, and has the intended package and policy.
  5. Check NAS port or interface bindings with the exact reported interface value.
  6. Confirm firewall rules allow the required UDP traffic between NAS and server.

When session or usage data is missing, confirm that the NAS sends Accounting-Start, interim-update, and Accounting-Stop packets to the configured accounting port. When a forced disconnect fails, troubleshoot the router-facing CoA port instead.

Do not change server configuration casually

FreeRADIUS, PostgreSQL, and the application share authorization and accounting behavior. Use the Dream Radius panel for normal network and subscriber configuration. Server-level changes should be planned, backed up, tested, and performed by an administrator with access to the deployment environment.

Dream Radius ISP CRM