PPPoE Management

01How PPPoE flows through the system

The router terminates the PPPoE tunnel; Daddy SAS decides whether the subscriber may connect and under which policy.

• The subscriber device discovers the PPPoE server on the MikroTik router (PPPoE discovery is router-local).
• The router forwards the credentials to Daddy SAS over RADIUS.
• Daddy SAS validates the account and returns the service profile: rate limit, IP assignment, timeouts.
• Accounting then tracks the live session until Stop.

02Account lifecycle

• Create, edit, suspend, reactivate, expire and delete PPPoE accounts.
• Username/password management with package assignment.
• Subscriber groups and account restrictions.
• Bulk import/export tooling for mass operations and migrations.

03Profiles & addressing

• Service profiles with speed and data limits and burst mode.
• IP pools and per-subscriber static IP assignment (Framed-IP-Address).
• Policy inheritance with per-subscriber overrides.
• MAC binding ties an account to a device (Calling-Station-Id).

04Sessions, expiry & renewal

• Session monitoring and concurrent-session restrictions.
• Usage accounting, active-session termination and renewal workflows.
• Expiration rules drive automatic rejection or disconnection once the account lapses.
• Centralized management across multiple PPPoE servers.

05Common connection failures

• Authentication failure on the client: check account state, credentials and NAS entry in the panel.
• Connects then drops: check Session-Timeout/Idle-Timeout values and quota exhaustion.
• Wrong speed: verify the package→profile mapping and that CoA is enabled on the router.