PPPoE Service Name Mismatches During Subscriber Setup

This guide covers PPPoE service name. Start with the checks below. Then compare your result with the example before changing a live service. A new subscriber can fail before a payment rule becomes relevant. Check the intended PPPoE service and client configuration before changing expiry dates or marking a payment unsuccessful.

PPPoE service name: practical checks

1. Compare the customer device's configured service requirements with the gateway.
2. Confirm the correct physical path and access interface.
3. Record discovery and authentication observations as separate stages.

PPPoE service name: a working example

If the customer device never reaches the expected service, adding more paid days cannot fix that stage. Preserve the entitlement while the technician resolves discovery.

First, write down the starting state and the expected result. Then make one controlled change. Next, compare the result with the example above. Finally, record what changed and who should follow up. Keep private account details out of shared notes.

Where LinkDesk fits

LinkDesk includes local PPPoE workflows and a FreeRADIUS bridge. These require deployment testing. Enforced PPPoE or RADIUS data quotas and strict global simultaneous-session enforcement for RADIUS PPPoE are not included in the documented current scope.

For the tool or product details behind this guide, see MikroTik PPPoE documentation. The checklist and example above are WayaDesk’s operating guidance.