Table of Contents
Principles of RADIUSdesk Profiles
Introduction
Each Voucher, Permanent User and BYOD Device will have a profile attached to it. Profiles are used to control the behavior of the NAS device through which a user (Voucher, Permanent User or BYOD Device) connects to the network.
This will include the following:
- Limiting the bandwidth.
- Limiting the total data available over a time period e.g. a monthly data cap.
- Preventing the user from connecting before a specified date.
- Preventing the user from connecting after a specified date.
RADIUSdesk installs with a few Profiles ready to choose from when you add a new Permanent User. But you are still able to create your own custom Profile.
Profiles with Profile Components
- A Profile will have one or more Profile components assigned to it with a certain priority level set for each component.
- Profile components can consist of:
- Time and Data counters to limit the total data or time usage over a specified period of time.
- Attributes that will instruct the NAS to apply certain limitations like the bandwidth.
Some sample Profile Components
This section will list a few sample Profile components which can be used as a reference when creating your own ones.
Instead of combining counters and throttles, simply create a few building block profile components which you can mix and match in the profiles.
1Gb Data - Never Reset
| Attribute | Check or Reply | Operator | Value | Comment |
|---|---|---|---|---|
| Rd-Total-Data | Check | := | 1000000000 | Multiply by 1024 if you want to be more technical  |
| Rd-Reset-Type-Data | Check | := | never | |
| Rd-Cap-Type-Data | Check | := | soft | Options are hard or soft. Soft will not cut the user off if they are over the limit |
| Fall-Through | Reply | := | Yes | Required to group these components together |
500Mb Data - Reset monthly
| Attribute | Check or Reply | Operator | Value | Comment |
|---|---|---|---|---|
| Rd-Total-Data | Check | := | 500000000 | Multiply by 1024 if you want to be more technical |
| Rd-Reset-Type-Data | Check | := | monthly | |
| Rd-Cap-Type-Data | Check | := | hard | Options are hard or soft. Soft will not cut the user off if they are over the limit |
| Rd-Reset-Day | Check | := | 25 | The counter will start at zero again in the 25th each month |
| Fall-Through | Reply | := | Yes | Required to group these components together |
250Mb Data per day - Reset daily
| Attribute | Check or Reply | Operator | Value | Comment |
|---|---|---|---|---|
| Rd-Total-Data | Check | := | 250000000 | Multiply by 1024 if you want to be more technical |
| Rd-Reset-Type-Data | Check | := | daily | |
| Rd-Cap-Type-Data | Check | := | hard | Options are hard or soft. Soft will not cut the user off if they are over the limit |
| WISPr-Bandwidth-Max-Up | Reply | := | 384000 (384kb/s) | Multiply by 1024 if you want to be more technical |
| WISPr-Bandwidth-Max-Down | Reply | := | 384000 (384kb/s) | Multiply by 1024 if you want to be more technical |
| Fall-Through | Reply | := | Yes | Required to group these components together |
Bandwidth limiting 384kb/s
| Attribute | Check or Reply | Operator | Value | Comment |
|---|---|---|---|---|
| WISPr-Bandwidth-Max-Up | Reply | := | 384000 (384kb/s) | Multiply by 1024 if you want to be more technical |
| WISPr-Bandwidth-Max-Down | Reply | := | 384000 (384kb/s) | Multiply by 1024 if you want to be more technical |
| Fall-Through | Reply | := | Yes | Required to group these components together |
2 Hours per day - Reset daily
| Attribute | Check or Reply | Operator | Value | Comment |
|---|---|---|---|---|
| Rd-Total-Time | Check | := | 7200 | This is in seconds |
| Rd-Reset-Type-Time | Check | := | daily | |
| Rd-Cap-Type-Time | Check | := | hard | Options are hard or soft. Soft will not cut the user off if they are over the limit |
| Fall-Through | Reply | := | Yes | Required to group these components together |
Counters that limit per device
- Sometimes we would like a data and/or time counter to be applied to each device connecting.
- This comes in handy with the Click-to-connect feature of the Dynamic Login Pages.
- One can then without much trouble assign a 50Mb daily limit to people visiting a coffee shop.
- RADIUSdesk also has an enhancement to the regular daily, weekly and monthly counters. You can specify how often the counter needs to reset.
- We can also specify the hour when the daily counter should reset. This is handy for hotels where people have to check-out before a certain hour and new people can check-in after that hour.
- Let us look at a few practical implementations.
50Mb Data per device - Reset each hour
| Attribute | Check or Reply | Operator | Value | Comment |
|---|---|---|---|---|
| Rd-Total-Data | Check | := | 50000000 | Multiply by 1024 if you want to be more technical |
| Rd-Reset-Type-Data | Check | := | dynamic | The dynamic type has to be used together with Rd-Reset-Interval-Data |
| Rd-Cap-Type-Data | Check | := | hard | Options are hard or soft. Soft will not cut the user off if they are over the limit |
| Rd-Reset-Interval-Data | Check | := | 3600 | Reset every 3600 seconds, thus one hour. |
| Rd-Mac-Counter-Data | Check | := | 1 | This counter will be enforced on each device connecting |
| Fall-Through | Reply | := | Yes | Required to group these components together |
500Mb Data - Reset every 12 hours
| Attribute | Check or Reply | Operator | Value | Comment |
|---|---|---|---|---|
| Rd-Total-Data | Check | := | 500000000 | Multiply by 1024 if you want to be more technical |
| Rd-Reset-Type-Data | Check | := | dynamic | The dynamic type has to be used together with Rd-Reset-Interval-Data |
| Rd-Cap-Type-Data | Check | := | hard | Options are hard or soft. Soft will not cut the user off if they are over the limit |
| Rd-Reset-Interval-Data | Check | := | 43200 | Reset every 12 hours (43200 seconds) |
| Rd-Mac-Counter-Data | Check | := | 1 | This counter will be enforced on each device connecting |
| Fall-Through | Reply | := | Yes | Required to group these components together |