Auth Logs | AltRadius CRM

The Auth Logs page is the record of every authentication attempt your customers' devices make against the RADIUS server. Each time a customer's router tries to come online, the NAS asks AltRadius to confirm the account. The result is one of two things:

Access-Accept , the identity and password checked out, and the connection is allowed. On an accept, AltRadius also hands the router the customer's authorization details (IP address, upload/download speed, rate limits) built from their current plan.
Access-Reject , the request was refused, usually because the username is unknown, the password is wrong, or the account isn't eligible to connect right now.

This is the first place to look when a customer says "I can't connect" , it tells you whether the attempt ever reached the server and, if it was rejected, why.

Operator guide

Access-Accept , the identity and password checked out, and the connection is allowed. On an accept, AltRadius also hands the router the customer's authorization details (IP address, upload/download speed, rate limits) built from their current plan.
Access-Reject , the request was refused, usually because the username is unknown, the password is wrong, or the account isn't eligible to connect right now.

This is the first place to look when a customer says "I can't connect" , it tells you whether the attempt ever reached the server and, if it was rejected, why.

Where to find it: Sidebar → Logs → Auth Logs.

What each column shows

Column	What it shows	Notes
Auth Date	When the authentication attempt was made.	Shown in your branch's timezone.
Username	The account the device tried to authenticate as.	If it resolves to a customer, it links to their profile with an online indicator; otherwise the raw username is shown.
Reply	The server's response, split into Authentication (did the identity/password pass) and Authorization (the details returned on an accept).	Two lines when both are present.
Router IP	The router (NAS) the request came through.	Links to that router's page.
MAC Address	The device's hardware address (Calling-Station-Id).	Links to MAC Lookup for the address; hovering a recognised address shows the manufacturer, OUI prefix, assignment type, and country.
Status	Accept (green) or Reject (red).	The headline outcome of the attempt.

Filter the list

The filter bar gives you six controls, and the page defaults to the last 24 hours until you pick a date range:

Filter	What it does
Entries per page	10, 25, 50, 100.
Status	All, Accept, or Reject.
Date range	Overrides the default 24-hour window.
Customer	Type at least two characters to search by username or name, then pick a customer to see only their attempts.
Routers	Multi-select by router , you pick by router name, and the log filters by that router's IP.
MAC address	Partial match on the device address. Press Enter or click away to apply.
Reject reason	Appears only when Status is set to Reject (a reject reason has no meaning for accepted attempts).

Why an attempt was rejected (reject reasons)

When you filter to rejects, you can narrow further by the reason the request was refused. This is the fastest way to separate a mistyped password from a genuine configuration problem.

Reject reason	Meaning
No account found	The username matches no account.
Username case mismatch	An account exists, but the device sent the username in the wrong letter case, so it was treated as unknown. See Diagnostics & Tools → RADIUS Auth Diagnostics to find and fix these.
Wrong password	The account exists but the password did not match.
No router linked	The account has no router association that would let it connect here.
No active service plan	The account has no active plan to authorize.
No partner assigned	The account is missing a required owner assignment.
Branch mismatch	The request does not belong to this branch.
Location not allowed	The account is not permitted to connect from this location.
Plan configuration error	The plan attached to the account is misconfigured and could not be authorized.
Internal error	The server hit an unexpected error while processing the request.
Other	A reject that does not fall into the categories above.

Troubleshooting / FAQ

A customer is being rejected but you're sure the account exists. Check the reject reason. A Username case mismatch is the usual culprit , the device is sending, say, John when the stored username is john. Fix the username on the device, or standardise the stored case. RADIUS Auth Diagnostics is purpose-built for spotting these across your whole base.
You see accepts here but the customer still has no working connection. Authentication succeeding only means the login was allowed. Confirm the live session and traffic in Usage Logs; a recent disconnect in RADIUS Logs may mean they were dropped and haven't reconnected.
There is no export or print button. This page is view-only , filter and read on screen.