{% extends "radius/base.html" %} {% load crispy_forms_tags %} {% load report %} {% block content %}

Search in radius error logs

Search hints
{% crispy form %}
{% if form.is_bound %} {% if result %}
{% for desc in field_desc %} {% endfor %} {% for row in result %} {% for field in row %} {% if not forloop.first %} {% endif %} {% endfor %} {% empty %} {% endfor %}
{{ desc }}Info
{{ field|safe }} Details
No results found
{% else %} {% if not form.errors %}

No result

{% endif %} {% endif %} {% endif %} {% block radius-helper %}

Radius log search hints and information

Search string

The search string allows wildcards, e.g. you can search for dat3* to search all usernames starting with dat.

Query fields
Log entry types
Common messages explained
"Login incorrect: [host/PEROTTO] (from client unis port 50010 cli 00-10-60-76-AA-4F)"
The computer uses default values from Microsoft, and is therefore not correctly set up for 802.1x. "PEROTTO" is in this case the computer name. The "host/" part informs that this is host based authentication.
"Reply from home server 129.242.5.142:3001 - ID: 251 arrived too late for request 674132. Try increasing 'retry_delay' or 'max_request_time'"
Time-to-live for a buffered request timed out: It took too long to get an answer from the authentication server, or to finish a request.
"No outstanding request was found for proxy reply from home server xxx.xxx.xxx.xxx:xxxx - ID xxx"
Also related to timeouts, shouldn't be anything to worry about.
"Dropping conflicting packet from client clientname:1646 - ID: 15 due to unfinished request 709815"
Harmless messages that occur when the NAS'es (switches) resends a request before radius has replied to the previous request. Happens because of its own timeout.
"Rejecting request 709815 due to lack of any response from home server aasgardvn:1646"
This message will usually follow, and be related to, the previous message.
{% endblock %} {% endblock content %}