Logs and diagnostics

These pages are for the network and support teams when Connection check is not enough. In the menu they are under the Logs group.

Which one do I need?

Question	Page
When and how did this subscriber connect, or fail to?	Connection attempts
Why was this username’s sign-in rejected?	User auth log
Are routers sending broken or unknown packets?	RADIUS diagnostics
Did the disconnect command reach the router?	Network operations
Did part of the system report an error?	System events

Connection attempts

Follows each connection attempt from start to finish:

Request → Auth → Acct start → Online → Interim → Closed

Search for a username and choose a time window (15 minutes, 1 hour, 24 hours, 7 days). The Outcome column sums it up:

Outcome	Meaning
Session online / Session active	All good.
Authentication rejected	See the Reason code; the same reasons as in Connection check.
Waiting for accounting	Sign-in was accepted and is waiting for the router’s start report.
Accounting-Start missing	The router did not send accounting — see MikroTik setup.
Session ended	The subscriber disconnected.
Connection match is ambiguous	More than one session may match these records; check carefully.

User auth log

Every sign-in attempt and Farava’s decision (Accepted or Rejected), newest first. For each attempt: time, username, router, source IP, and Reason code. Filter by Result to see only rejected sign-ins.

RADIUS diagnostics

Warnings and errors from the RADIUS server, for example a packet from an address that does not belong to any registered router (usually a wrong source IP or NAT). The overall health of this area is shown at the top.

Network operations

Every command Farava sends to a router — Disconnect or Apply rate — is recorded here. You reach it from disconnect messages and service pages.

Command status	Meaning
Pending / In progress	Being sent
Succeeded	The router confirmed it
Retry scheduled	It did not arrive last time; it is resent automatically
Failed	Did not arrive after several tries
Superseded	A newer command replaced it

For a failed command, first fix the router’s disconnect settings and firewall, then select Retry delivery. A router’s confirmation alone does not prove the subscriber was disconnected; check under Sessions that the session actually Closed.

System events

Errors and warnings from Farava’s background parts, by severity (Info, Warning, Error, Critical). If you see a Critical event or errors keep repeating, contact the Farava team and send the event’s Code and Time.