Appearance
Policies
Policies define the RADIUS attributes that Dream Radius applies through a package. Use them to control subscriber speed, session, address, and other network-access rules.
How policies work
A policy is a named group of RADIUS attributes. When a customer is activated on a package, Dream Radius uses that package's policy to build the rules the RADIUS server evaluates for the customer.
For example, a policy for a 20 Mbps PPPoE plan might contain a vendor attribute such as Mikrotik-Rate-Limit with a value of 20M/20M.
Create a policy
- Open Policies and click Add Policy.
- Enter a clear, reusable policy name, for example
PPPoE 20 Mbps. - Add one or more RADIUS attributes.
- For each attribute, select the source, attribute name, operator, value, and type.
- Save the policy, then select it when you create or edit a package.
Policy names are unique within an ISP, so different ISPs can use the same name without sharing configuration.
Add RADIUS attributes
Choose From Vendor to select an attribute from an installed RADIUS dictionary, or Custom Attribute to enter an attribute name yourself. The source choice helps operators manage the form; the attribute, operator, value, and type are the values that define the RADIUS rule.
| Field | Meaning |
|---|---|
| Attribute | The RADIUS property to evaluate or return, such as Mikrotik-Rate-Limit. |
| Operator | How RADIUS applies the value, commonly := to set it. |
| Value | The value sent or checked, such as 20M/20M. |
| Type | Reply returns a value to the NAS; Check tests a condition during authentication. |
Use the vendor dictionary whenever it contains the needed attribute. Custom attributes are useful for attributes added by your NAS or a vendor-specific dictionary.
Dictionaries and vendors
The policy form can list the Standard RADIUS attributes and vendor attributes that have been loaded into Dream Radius. Administrators can upload a compatible RADIUS dictionary or sync the server's system dictionaries when an attribute or vendor is missing.
Only add attributes that your NAS and RADIUS configuration support. An unknown or invalid attribute can prevent the intended access rule from being applied.
Edit and delete safely
Editing a policy updates the attributes used by packages that reference it. Test changes with a non-production customer or during a maintenance window, then reconnect a test customer to confirm the NAS receives the expected rules.
Before deleting a policy, first move or update every package that uses it. The system rejects deletion when packages still reference the policy.
Use the policy list to search, review attributes, edit policies, and export the ISP's policy configuration when your role permits it.
Keep policies focused
Create policies around a single service profile—such as PPPoE 20 Mbps or Hotspot 10 Mbps—then reuse them across packages with the same RADIUS behavior.