Technical Documentation
Packages & Bandwidth Control
Speed limits, quotas, burst mode and FUP.
Speed limits, quotas, burst mode and FUP.
01Package model
- Download/upload limits; symmetric and asymmetric packages.
- Data-volume restrictions and burst configurations.
- Daily, weekly and monthly quotas with Fair Usage Policy (FUP) support.
- Shared or dedicated bandwidth policies; IP pools; policy inheritance with per-subscriber overrides.
02How enforcement works
Daddy SAS does not shape traffic itself — it instructs the NAS, which enforces the policy on the subscriber session.
- Speed limits are delivered to MikroTik as RADIUS authorization attributes (e.g. Mikrotik-Rate-Limit) or applied through router-side profiles.
- Data quotas are counted from RADIUS accounting octet counters.
- Time restrictions are enforced via Session-Timeout/validity rules.
- Mid-cycle package changes apply to a live session without disconnecting it (CoA).
03Policy table
| Policy | Mechanism | Enforced by |
|---|---|---|
| Speed limit (up/down) | Rate-limit attribute / router profile | NAS queue |
| Burst mode | Profile parameters | NAS queue |
| Data quota / FUP | Acct octet counters | Daddy SAS accounting + session control |
| Daily/weekly/monthly caps | Quota schedule | Daddy SAS accounting |
| Session time limit | Session-Timeout | NAS |
| Concurrent sessions | Simultaneous-use check | Daddy SAS authorization |
04Troubleshooting policy issues
- Subscriber gets wrong speed: check the package→profile mapping and whether the NAS honors the attribute.
- Policy change not applied: enable "radius incoming" (CoA) on the router.
- Quota never trips: missing interim accounting — set a reasonable interim-update interval on the NAS.
Daddy SAS manages subscriber policies — it does not replace your MikroTik queue design for backbone shaping.