Start with the login path
CPE / PPPoE client
→ MikroTik PPPoE server (NAS)
→ RADIUS Access-Request
→ FreeRADIUS: identity lookup → authentication → access policy
← Access-Accept, Access-Reject or Access-Challenge
← MikroTik completes or refuses the PPP login
PPPoE discovery and PPP negotiation happen before usable internet access. If discovery never reaches the NAS, investigate the access link, VLAN and PPPoE service first: there may be no RADIUS request to find. An Access-Challenge asks for another authentication step; it is not a rejection.
Check that this subscriber actually uses RADIUS. RouterOS can use a matching local PPP account instead, and PPP RADIUS authentication must be enabled. See MikroTik's PPP AAA documentation. For integration planning, see the FreeRADIUS guided-pilot scope.
Access-Reject is a result, not a standard reason code. The client may display only “authentication failed”. An optional Reply-Message can help, but the server's policy trace is the evidence. Missing or invalid replies belong to a different branch of the diagnosis. Do not present all seven cases below as packets that contain Access-Reject.
Collect one attempt, at three places
Agree on a short test window and record the timezone, subscriber reference, NAS and authentication method. Use a test account where possible. Correlate the timestamp, source address and server request identifier; a packet identifier alone is reused and is not a unique customer reference.
1. MikroTik RouterOS
Read the existing logs and counters; these examples change no configuration:
/log print where topics~"ppp|radius"
/ppp aaa print
/radius monitor [find where address=192.0.2.10] once
The documentation address 192.0.2.10 stands for your RADIUS server. Select the relevant configured entry. Compare requests, rejects, timeouts and bad-replies before and after the attempt: cumulative counters can include other subscribers. Existing log topics may not include detailed RADIUS traces. Have the network owner capture a short, controlled trace if more evidence is needed; do not enable unrestricted credential-bearing debug output on a busy router.
A rise in rejects supports the rejection branch. timeouts points to no valid response within the configured time. bad-replies calls for checking reply validation and the NAS/RADIUS relationship. See RouterOS RADIUS counters and client settings.
2. FreeRADIUS logs
Read the configured service journal or radius.log; paths and verbosity vary by distribution. Find the matching request, then the first relevant failed module or policy decision before the final reply. A final “Sent Access-Reject” line does not explain why it happened.
For a reproducible isolated lab test, FreeRADIUS 3.x debug mode (radiusd -X, or freeradius -X on some distributions) shows the decision path. Do not start a second daemon on occupied ports or stop a production service to follow this guide. Debug output can expose credentials and personal data: retain it privately, minimise the excerpt, and redact before sharing. See FreeRADIUS debug-output guidance.
These are fabricated, shortened teaching examples, not exact output guaranteed for every version. subscriber-demo is fictional; all IP addresses are documentation addresses. Credential-bearing attributes are omitted entirely.
RouterOS, 12:00:00: ppp authentication failed (subscriber-demo)
FreeRADIUS (42): Received Access-Request from 198.51.100.20
FreeRADIUS (42): identity lookup: subscriber-demo found
FreeRADIUS (42): authentication module: credential verification failed
FreeRADIUS (42): Sent Access-Reject to 198.51.100.20
A different attempt might end before authentication:
FreeRADIUS: Ignoring request from unknown client 198.51.100.21
RouterOS: RADIUS request timed out
3. SQL post-auth history: radpostauth
When SQL post-auth logging is enabled for the accept/reject paths, a typical FreeRADIUS 3.x schema records the username, reply and time in radpostauth. It does not necessarily record the underlying reason. Read only the required fields in your authorised operator tool:
SELECT username, reply, authdate
FROM radpostauth
WHERE username = 'subscriber-demo'
ORDER BY authdate DESC
LIMIT 10;
Check the local schema before running the query. Do not use SELECT *: some stock schemas include a pass column, and custom logging may store sensitive attributes. Never export credential columns into a support ticket. An Access-Reject row establishes the recorded result; pair it with the request's server evidence. No row can mean disabled logging, SQL failure or an earlier failure. See the FreeRADIUS 3.2 SQL post-auth query configuration.
Common reasons and the next safe action
| Suspected reason | What the support agent sees | What it means | What to do next |
|---|---|---|---|
| Wrong password | Generic PPP authentication failure; server authentication module fails and sends Access-Reject. | The presented credential did not verify, or the stored credential format cannot support the negotiated PAP/CHAP/MS-CHAP method. | Confirm the exact username, realm and method. Use the approved credential-reset process if needed; never ask for a password in a ticket. Retest once. |
| Unknown user | Lookup finds no matching user; policy eventually rejects. | Typo, realm rewriting, wrong identity store or missing provisioning. | Compare the normalised login with the intended account and lookup backend. Repair the mapping; do not create an unexplained duplicate account. |
| Suspended or expired account | Credentials may verify, then an account-status or expiry rule rejects. | A local access policy denies this service. “Paid” in one system does not prove the access policy was updated. | Check service state, expiry timezone and the authoritative payment/policy record. Ask the authorised owner to correct the state; do not bypass it. |
| Simultaneous-use limit / stale session | Server session check reports the configured limit has been reached. | A real second session or stale accounting may consume the permitted session count. | Compare the live NAS session with accounting, including NAS, session ID and last update. Close stale state only after proving it is stale. Never clear every subscriber's session. |
| Unknown NAS / RADIUS client | FreeRADIUS ignores a request from an unknown client; the router often times out. | The packet source is not a recognised client. This normally is not an Access-Reject. | Check the source IP seen by the server, including NAT, against the authorised client definition. NAS-IP-Address inside the packet is not a substitute for the source check. |
| Shared-secret mismatch | Invalid authenticator warnings, bad-replies, timeout, or in some PAP cases a credential failure. | Packet authentication or credential decoding may fail. An Access-Accept in a server log can still be unusable at the NAS. | Have the authorised operator verify both ends through the secure credential workflow and check Message-Authenticator compatibility. Do not paste secrets or disable validation to make it work. |
| RADIUS unreachable | Requests/retries/timeouts rise; no matching server request, or the response never reaches the router. | Routing, firewall, listener, overload or return-path failure; not proof of rejected credentials. | Check the configured transport and authentication endpoint, source route, listener and return traffic. UDP authentication commonly uses 1812; accounting on 1813 is separate. A successful ping alone proves neither. |
Simultaneous-use enforcement depends on your server policy and reliable accounting; it is not an automatic diagnosis for every abandoned PPP session. Consult FreeRADIUS simultaneous-use guidance.
Close the support call with evidence
- Record the observed branch: reject, invalid response, timeout, or no request.
- Identify the server rule or network check that explains this attempt. If no explanation is proven, record what is still unknown and escalate with a sanitised excerpt.
- Make one authorised correction, then repeat the login.
- Verify both the accepted authentication and an established PPP session, address assignment and usable traffic. An Access-Accept alone does not prove restored internet.
- Record the result and remove temporary diagnostic logging through the operator's normal change process.
A useful handoff says: “Attempt at 12:00 UTC reached the NAS and FreeRADIUS; the expiry rule rejected it. Account owner to review expiry, then support to retest.” It does not say “RADIUS is broken” or attach a raw credential-bearing dump.
Where ISPAgents fits
ISPAgents offers basic subscriber records and device assignment. The Existing FreeRADIUS adapter is guided pilot, with a Status-Server probe; SQL/API sync, accounting import, policy write-back and CoA remain planned. An automatic Access-Reject explainer is planned, not a shipped capability. This guide describes manual operator diagnosis, not an automated ISPAgents workflow.
Discuss a guided pilot to agree which evidence your support team needs and what must still be validated. Continue with MikroTik integration scope and the FreeRADIUS versus managed RADIUS guided-pilot evaluation.
Frequently asked questions
Does Access-Reject always mean a wrong password?
No. An account rule, authentication-method mismatch or session limit can also cause a rejection. Correlate the attempt with the server's policy and authentication logs.
Why is there no radpostauth row?
SQL post-auth logging may be disabled, failing or configured differently. Unknown-client and unreachable-server failures can occur before post-auth. An empty table does not prove that no attempt occurred.
Can Access-Accept still leave a subscriber offline?
Yes. A rejected reply at the NAS, PPP negotiation, address allocation, routing, DNS or a later disconnection can prevent usable internet access. Follow the same attempt through session establishment.
Plan a guided pilot
Agree on scope, evidence and limitations before connecting your network.
Discuss a guided pilot